You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 29, 2019. It is now read-only.
Even if my public.scss is completely empty, it looks likes like the generated public.css is identical to app.css. I'm obviously doing something incredibly wrong...
The text was updated successfully, but these errors were encountered:
Since path was dynamic, I'm guessing whatever engine webpack was using decided that all files ending in .js would be included - thus including the app.js which lived within the same root directory. By explicitly defining the path name (while leaving fileName dynamic), it worked properly.
I can get the example to run fine, but for the life of me, I can't make mine work.
I have 2 entry points - public.js and app.js, which require the corresponding public.scss and app.scss respectively.
webpackConfig:
Even if my public.scss is completely empty, it looks likes like the generated public.css is identical to app.css. I'm obviously doing something incredibly wrong...
The text was updated successfully, but these errors were encountered: