options.sourceMap isn't set - CLI 2.0.0

[timarney]

Trying to track down why this error might be happening in dev. CLI version 1.4.1 was fine.

Seeing the following when I try to start the dev server.

@ ./node_modules/preact-cli/lib/lib/entry.js
⚠ WARN ./node_modules/preact-cli/lib/lib/webpack/proxy-loader.js?{"proxy_loader":{"loader":"sass-loader","cwd":"my-dir-here"},"sourceMap":true}!./src/components/menu/style.scss
(Emitted value instead of an instance of Error)

Previous source map found, but options.sourceMap isn't set.
In this case the loader will discard the source map entirely for performance reasons.
See https://github.com/postcss/postcss-loader#sourcemap for more information.

Details
npm 5.5.1
node 8.7.0

[euangoddard]

I have exactly the same issue following the same upgrade path.

npm 5.5.1
node 8.1.3

[lukeed]

This was a change within postcss-loader that I overlooked. PR open, just waiting for another team member to approve & then we'll publish a patch release.

Thanks guys.

[lukeed]

Now available in 2.0.1

[timarney]

Hi @lukeed

Based on your PR I think my issue is with the proxy-loader. If I update as you did to use isProd vs true that seems to work. Not sure is there is a reason for that to be forced to true.

use: [{
					loader: 'proxy-loader',
					options: {
						cwd,
						loader: 'sass-loader',
						options: { sourceMap: isProd }
					}
				}]

[lukeed]

Hey, proxy-loader just passes the options along to the loader its proxying. They're all set to true to always enable it, initially.

In 1.4, the isProd value was still the final determinant.

The proxy-loader settings haven't changed from 1.4 to 2.0 --- only postcss-loader has & the last PR patches that difference.

Thanks!

[euangoddard]

@lukeed I've just updated to 2.0.1 and am still getting errors:

(Emitted value instead of an instance of Error) 

 ⚠️  PostCSS Loader

Previous source map found, but options.sourceMap isn't set.
In this case the loader will discard the source map entirely for performance reasons.
See https://github.com/postcss/postcss-loader#sourcemap for more information.```

[lukeed]

@euangoddard Can you verify that both your global and local copies are on 2.0.1?

[timarney]

I still get the warning as well with the 2.0.1 version globally and locally (dev mode).

The server does run but the warning happens for each sass file.

If I log out the options (via preact.config.js) for the sass-loader it shows as

{ sourceMap: true }

If I modify the config -> sass-loader options to { sourceMap: false } the warning does go away.

[lukeed]

Can you guys post a reproduction somewhere? I'm not getting it. Thanks!

[timarney]

Let's see what @euangoddard says ... than I'll see if I can reproduce in a test repo.

[timarney]

Sorry is the --sass flag gone?

preact create testproject --sass

[timarney]

@lukeed had a sec to reproduce here's a test repo:
https://github.com/timarney/preactcli-sass

Warning in dev

⚠ WARN ./node_modules/preact-cli/lib/lib/webpack/proxy-loader.js?{"cwd":"dir-here-preactcli-sass","loader":"sass-loader","options":{"sourceMap":true}}!./src/style/index.scss
(Emitted value instead of an instance of Error)

 ⚠️  PostCSS Loader

Previous source map found, but options.sourceMap isn't set.
In this case the loader will discard the source map entirely for performance reasons.
See https://github.com/postcss/postcss-loader#sourcemap for more information.

The build works - text in red