-
Notifications
You must be signed in to change notification settings - Fork 216
Service worker warns: No directory provided. Skipping CSS generation #298
Comments
Relevant changes that I found:
The message started to appear since |
Any idea how to fix it? |
I hid the warning message by adding this line into the (warning.plugin === 'css' && warning.message === 'No directory provided. Skipping CSS generation') || Full const onwarn = (warning, onwarn) =>
(warning.code === 'MISSING_EXPORT' && /'preload'/.test(warning.message)) ||
(warning.code === 'CIRCULAR_DEPENDENCY' && /[/\\]@sapper[/\\]/.test(warning.message)) ||
(warning.code === 'THIS_IS_UNDEFINED') ||
(warning.plugin === 'css' && warning.message === 'No directory provided. Skipping CSS generation') ||
onwarn(warning) |
We should identify and remove the problem. This is not a good idea. I think :) |
yeah sure. |
Hi, I just updated Sapper to 0.29.1 and I get this message What's the issue and.. how could I fix that ? |
[Disclaimer: I did not test to see if the latest version of the Sapper template still results in this warning] If you aren't using the latest version of this Sapper template, then your config hasn't been updated to avoid the warning. So, start over using the latest version of the template or compare its config files and dependencies to yours to see if you can solve the error without starting over. |
The message |
A fix has been merged to the master branch, but hasn’t been released yet. To get Sapper with the latest commits (even if not part of a tagged version) you can install it directly from the master branch on GitHub: |
Been seeing this warning lately, not sure what has led to it
Presumably it's something that can be resolved in the rollup config
The text was updated successfully, but these errors were encountered: