Service worker warns: No directory provided. Skipping CSS generation

[mattpilott]

Been seeing this warning lately, not sure what has led to it

Presumably it's something that can be resolved in the rollup config

[gustavopch]

Relevant changes that I found:

• https://github.com/sveltejs/sapper/commit/6b143313f422ec670f7cc13ebfc415e2aa1d89e1#diff-571921ec068c7f3022a3c9625c52489e110fd6298971fcf4cadabcea81434a0bR158
• https://github.com/domingues/rollup-plugin-css-chunks/commit/e7483217908a721cef30ae450bf8337043acd90f#diff-dcdc3e0b3362edb8fec2a51d3fa51f8fb8af8f70247e06d9887fa934834c9122R97

The message started to appear since sapper@0.29.0.

[yashsamit]

Any idea how to fix it?

[jessaleks]

Been seeing this warning lately, not sure what has led to it

Presumably it's something that can be resolved in the rollup config

but where 🤔

[Pytal]

I hid the warning message by adding this line into the onwarn function of rollup.config.js

  (warning.plugin === 'css' && warning.message === 'No directory provided. Skipping CSS generation') ||

Full onwarn function:

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)

[yashsamit]

We should identify and remove the problem. This is not a good idea. I think :)

[didiermun]

We should identify and remove the problem. This is not a good idea. I think :)

yeah sure. I would like also to get on that solution on that problem.

[didiermun]

Been seeing this warning lately, not sure what has led to it Presumably it's something that can be resolved in the rollup config

but where 🤔

when you are running the sapper project it will

[tri-nga]

Hi, I just updated Sapper to 0.29.1 and I get this message No directory provided. Skipping CSS generation, as in the screenshots above.

What's the issue and.. how could I fix that ?

[babichjacob]

Hi, I just updated Sapper to 0.29.1 and I get this message No directory provided. Skipping CSS generation, as in the screenshots above.

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.

[tri-nga]

Hi, I just updated Sapper to 0.29.1 and I get this message No directory provided. Skipping CSS generation, as in the screenshots above. 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 No directory provided. Skipping CSS generation showed up after I updated the packages to the latest version available. I did solve going "back" to the Sapper template packages version.

[silllli]

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: npm install -D sveltejs/sapper#master