faulty webpack configuration is creating strange files on wrong places #18404
Unanswered
alexanderadam
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm working on an old Middleman project (a static site generator) where the processed CSS is meant to be published in
build/content/
, fonts inbuild/content/fonts/
, images inbuild/content/images/
and the processed JS is meant to be published tobuild/scripts/
.With a few exceptions, all custom JS was merged into
build/scripts/application.js
and all custom CSS intobuild/content/application.css
.Click to see the list of files before
However, recently there was a migration from very old dependencies to current ones, including a migration from the internal asset pipeline to webpack.
The configuration seem to have some bugs though and now there are random files in the build directory and some of them doesn't even make any sense:
Unfortunately the person who created that configuration left the project and I have no idea what might be looking wrong.
Hence I'd be super grateful for any advice!
Click to see the buggy webpack configuration
Thank you in advance!
EDIT: Nevermind. I figured it out using GitHub Copilot
Beta Was this translation helpful? Give feedback.
All reactions