-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@parcel/bundler-default: The expression evaluated to a falsy value (CSS modules and non-modules) #8716
Comments
cc @AGawrys |
same here with parcel@2.8.2 |
+1 |
Should be fixed by #8762 |
I see that this is closed and should have been fixed by 2.8.3. However, after upgrading from 2.8.0 to 2.8.3, I still see the same error:
What should I look for in my project to see what might be unique from the cases that were already fixed? |
Might just be the same symptom. Do you have a repro or repo I could look at? @shepmaster |
Here is a minimized example: repro.zip. Unzip it, run My gut tells me that it has to do with using the |
I also have this problem, it's definitely caused by css modules It looks like the file referenced in the Using @shepmaster's repro from above and then removing the statement: asset.addDependency({
specifier: ref.specifier,
specifierType: 'esm',
}); From the It looks like this was added fairly recently to improve css import ordering: |
Should be fixed by #8885 |
@devongovett how to get the fixed version for this? Should there be a patch version release for this? |
I got this error when running Basically |
There will be a release including the fix very soon |
why is this closed without being fixed |
i have also got this type of error but i just cleared my parcel cashe and the error was resolved |
🐛 bug report
In particular circumstances I get following error when building my project:
🎛 Configuration (.babelrc, package.json, cli command)
Minimal example is here
Key points: if there is non-module CSS file and more than one module CSS files in project - build will fail.
Build command is
🤔 Expected Behavior
Build should not fail. I don't think this CSS structure is wrong or unobvious; at least it should lead to better error than just "assertion failed"
😯 Current Behavior
Build fails with following stack trace:
🔦 Context
I'm just developing some websites lol
💻 Code Sample
Minimal example is here
🌍 Your Environment
The text was updated successfully, but these errors were encountered: