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
Today I came across an issue that my npm build command does not generate any build files. I narrow down the issue and I found it could be some errors in my code. But I thought webpack should at least log something, instead of nothing.
I test this issue with a clean clone of this repo, and add below to any js files.
import'/something/does/not/exist'
This path has nothing. Then when I do npm build, there is no build files and no errors on the console.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Today I came across an issue that my
npm build
command does not generate any build files. I narrow down the issue and I found it could be some errors in my code. But I thought webpack should at least log something, instead of nothing.I test this issue with a clean clone of this repo, and add below to any js files.
This path has nothing. Then when I do
npm build
, there is no build files and no errors on the console.How do I configure webpack to show errors?
Beta Was this translation helpful? Give feedback.
All reactions