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 has been archived by the owner on Apr 7, 2021. It is now read-only.
As seen, npx webpack should produce some webpack commands.
On the other hand, when I run webpack directory, it just works.
C:\WorkSpace\prj\study\webpack\webpack-demo>node_modules\.bin\webpack
Hash: 029a3c105afe97d2be1b
Version: webpack 4.42.1
Time: 298ms
Built at: 2020-03-26 15:46:51
Asset Size Chunks Chunk Names
main.js 72.1 KiB 0 [emitted] main
Entrypoint main = main.js
[1] d:/WorkSpace/prj/study/webpack/webpack-demo/src/index.js 242 bytes {0} [built]
[2] (webpack)/buildin/global.js 472 bytes {0} [built]
[3] (webpack)/buildin/module.js 497 bytes {0} [built]
+ 1 hidden module
WARNING in configuration
The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment.
You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/configuration/mode/
C:\WorkSpace\prj\study\webpack\webpack-demo>
When
See above
Where
I'm not node.js developer guy 😢 with just a handful amount of javascript knowledge, so I did kinda console.log debugging of this issue. and figured out followings code findNodeScript() in index.js does not work correctly
With that script, the findNodeScript() cannot find actual node script's path which is supposed to be like C:\prj\webpack-demo\node_modules\webpack\bin\webpack.js in my case.
How
Current Behavior
See above
Steps to Reproduce
See above
Expected Behavior
findNodeScript() should parse the correct node script file path from script in win32 environment. See above.
Who
n/a
References
n/a
The text was updated successfully, but these errors were encountered:
What / Why
In my Windows 10 Box, I cannot run
npx webpack
produces following outputssee following cmd log.
As seen,
npx webpack
should produce somewebpack
commands.On the other hand, when I run webpack directory, it just works.
When
See above
Where
I'm not
node.js
developer guy 😢 with just a handful amount of javascript knowledge, so I did kindaconsole.log
debugging of this issue. and figured out followings code findNodeScript() in index.js does not work correctlyIn that function,
actually cannot see the
cmd
pattern in batch script(c:\prj\webpack-demo\node_modules\.bin\webpack.cmd
script in my case) of which contents isWith that script, the
findNodeScript()
cannot find actual node script's path which is supposed to be likeC:\prj\webpack-demo\node_modules\webpack\bin\webpack.js
in my case.How
Current Behavior
See above
Steps to Reproduce
See above
Expected Behavior
findNodeScript()
should parse the correct node script file path from script in win32 environment. See above.Who
References
The text was updated successfully, but these errors were encountered: