Issue with `fourseven:scss@5.0.0-alpha.1` and Internal Meteor Packages

[LionelGuerin]

Describe the Bug
I'm using fourseven:scss with internal Meteor packages, and since version 5.0.0-alpha.1, I've encountered the following problem:

   While building for web.browser:
   /packages/testlocal_scss/client/style_test.scss: Scss compiler client/style_test.scss: no such file or directory

To Reproduce
I’ve created a project to reproduce this behavior, available here: https://github.com/LionelGuerin/meteor_forkedseven_scss

In the folder sass_tests/sass, I'm using fourseven:scss@5.0.0-alpha.1.

To reproduce the error, run the following commands:

git clone git@github.com:LionelGuerin/meteor_forkedseven_scss.git
cd meteor_forkedseven_scss/sass_tests/sass
meteor --port 4000

Expected behavior
In the folder sass_tests/sass_forked, there is another Meteor app that uses a slightly modified version of fourseven:scss@5.0.0-alpha.1.
This custom package is located in:
sass_tests/sass_forked/packages/forkedseven_scss

The only change made is on line 183, where filePath is replaced in the compileAsync function:

output = await sass.compileAsync(inputFile.getSourceRoot()+ "/" + inputFile.getPathInPackage(), options);
// output = await sass.compileAsync(inputFile.getPathInPackage(), options);

I’m pretty sure this isn’t the correct way to do it, but I don’t know how to fix it properly (and that's why I haven’t made a PR).

Thank you in advance for your time and help ! :)

[github-actions]

Thank you for submitting this issue!

We, the Members of Meteor Community Packages take every issue seriously.
Our goal is to provide long-term lifecycles for packages and keep up
with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.

However, we contribute to these packages mostly in our free time.
Therefore, we can't guarantee your issues to be solved within certain time.

If you think this issue is trivial to solve, don't hesitate to submit
a pull request, too! We will accompany you in the process with reviews and hints
on how to get development set up.

Please also consider sponsoring the maintainers of the package.
If you don't know who is currently maintaining this package, just leave a comment
and we'll let you know

[illusionfield]

This is indeed a very possible issue. For some reason, I didn't consider that the package might be used without isImport.

api.addFiles('x.scss', 'client', { isImport: true });

Thanks for the detailed information! This makes it easy to investigate and fix the problem.

[illusionfield]

I have forked the test environment you created and extended it with additional variations to cover more possible use cases. Now, everything works flawlessly in all scenarios.

You can check it here:
https://github.com/illusionfield/meteor_forkedseven_scss

[illusionfield]

Hi,

The latest release is now available: fourseven:scss@5.0.0-alpha.3, which includes the fix.

@LionelGuerin please update and let me know if the issue still persists.

thx 😉