For questions please post on Stack Overflow and use the 'webpack' tag (http://stackoverflow.com/tags/webpack).
html files
webpack is running through scripts package.json
Here at stack also we have added the problem
even after deleting main.scss
still it is loading on web browser
Can you try doing an ES6-style import of your stylesheets in your main JS file?
i've seen problems when using multiple loaders on 1 file
regarding ES6-style import of your stylesheets in your main JS file?
is my directory structure
is the pages and I am running directly is it something wrong I am doing as I am novoice to webpack
now in the src folder I do changes in main.scss nothing
happened
we are running directly
just like putting in xampp server
@harshit786 I suspect your issue is not webpack, but Apache on Windows.
running
in package.json
Runnning without apache
still does not solve problem
I know with image imports in a JS file the import returns the path. I just have no idea how that translates to something imported in a CSS file.
@urbanmichal Admittedly, about a week after I started learning how to configure Webpack.. I switched to using
Encore as it does almost everything I needed. That said, if memory serves me right, I think you may have to use the url-loader along with your other CSS loaders to fix paths in CSS.
@johnmarinelli My biggest complaint about Encore is that once I started using it.. I wanted to use it for more than just web outputs.. and sadly it currently lacks the ability to configure the target output. I'm currently using an internal fork of Encore that I've modified for this purpose..
@johnmarinelli Most issues I've run into are more to do with how Webpack functions rather than anything else. E.g. I find Webpack's
externals option to be very lacking as it merely creates a wrapper around globally defined variables and provides no mechanism to actually include external libraries from a CDN. Thus, when the global variable is not defined it throws an error.
@harshit786 I think this is a case where you are simply using Webpack wrong. Just because you can reference Webpack outputs from the
dist folder doesn't mean you should. Doing so is often discouraged because it creates a client-side caching issue. I.e. the browser caches the page and it's assets separately. However, if the page has not been modified, the browser may not check if the assets have been. If you want to continue using static pages.. then I would recommend making your html files your Webpack entrypoints and using the html-loader in combination with the extract-loader. Encore doesn't support processing of HTML files so you would have tell it to load the additional loaders required to do so.