problems with extended webpack config in dev script (svgsprite plugin) about polymer-skeleton HOT 10 CLOSED

Hey @DanielRuf, can you please give us more details?
Are you getting the error for both commands?
Are you checking the correct browsers when running the commands? (check out the readme for more details)
Did you make any changes or it is a fresh copy of the skeleton?

I can't help without this kind of details.
Thanks!

from polymer-skeleton.

I am using Chrome 60 on Windows.
Both scripts throw this error.

It was a fresh copy.

Fresh dev in incognito mode:

(index):90 GET http://localhost:3000/module.bundle.js net::ERR_ABORTED
componentsReady @ (index):90
(anonymous) @ webcomponents-loader.js:61
requestAnimationFrame (async)
fire @ webcomponents-loader.js:59
(anonymous) @ webcomponents-loader.js:66
(anonymous) @ webcomponents-loader.js:74
A bad HTTP response code (404) was received when fetching the script.
:3000/sw.js Failed to load resource: net::ERR_INVALID_RESPONSE
(index):71 Error during service worker registration: TypeError: Failed to register a ServiceWorker: A bad HTTP response code (404) was received when fetching the script.

Fresh dev:module works but throws

(index):71 Error during service worker registration: TypeError: Failed to register a ServiceWorker: A bad HTTP response code (404) was received when fetching the script.

But is also very fragile when adding other webpack plugins eg for svg spritesheets.

I am using Windows 10 with Node 8 and npm 5.

from polymer-skeleton.

The requirement of the service workers does not make it easier for local testing.

from polymer-skeleton.

Also see https://github.com/DanielRuf/polymer-skeleton-svgsprites

from polymer-skeleton.

I am using Chrome 60 on Windows.

For developing on Chrome you need to run dev:module. As you said it works, and service workers are not generated for development with the current configuration, so it's simply a "not found" error that you won't have with a production build.
Anyway you can easily fix this 404 generating the service worker also for development or with better check before trying to register the workers (eg. an initialization script bundled with Webpack where you can check for the process.env.NODE_ENV variable).

But is also very fragile when adding other webpack plugins eg for svg spritesheets.

Do you have any specific error?

Anyway I would prefer a PostCSS plugin for working with SVG.

Maybe @equinusocio can help?

@DanielRuf if you don't have any other problem for loading the app with the dev and dev:module command please rename the issue so we can focus on the sprite plugin problem.

from polymer-skeleton.

No, in the normal dev mode the site still shows loading.

from polymer-skeleton.

For the "dev" command you should use a no-module browser like FireFox. Please check out the Readme for more details.

from polymer-skeleton.

Ok, then we just have the svgsprite issue left.

from polymer-skeleton.

Hey @DanielRuf, did you find a solution for your problem? I have updated Webpack, maybe now you can double check if this is still a problem. I'm closing for now, feel free to reopen!

from polymer-skeleton.

Will try to check then.

We stopped evaluating Polymer further as it introduced more issues compared to our React solutions.

from polymer-skeleton.