question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"npm run start" - Start Webpack server doesn't produce output

See original GitHub issue

When I run npm run start, to start the Webpack server, I get this output:

npm run start

@json-editor/json-editor@1.4.0-beta.0 start C:\GITHub\json-editor webpack-dev-server --config config/webpack.dev.js --progress

10% building 1/1 modules 0 activei 「wds」: Project is running at http://localhost:8080/ i 「wds」: webpack output is served from /dist/ i 「wds」: Content not from webpack is served from C:\GITHub\json-editor i 「wds」: 404s will fallback to /index.html i 「wdm」: Hash: 8f5eab5eadb3883f8836 Version: webpack 4.39.1 Time: 3590ms Built at: 2019-08-24 15:10:26 Asset Size Chunks Chunk Names jsoneditor.js 2.09 MiB jsoneditor [emitted] jsoneditor Entrypoint jsoneditor = jsoneditor.js [0] multi (webpack)-dev-server/client?http://localhost:8080 ./src/core.js 40 bytes {jsoneditor} [built] [./node_modules/strip-ansi/index.js] 161 bytes {jsoneditor} [built] [./node_modules/webpack-dev-server/client/index.js?http://localhost:8080] (webpack)-dev-server/client?http://localhost:8080 4.29 KiB {jsoneditor} [built] [./node_modules/webpack-dev-server/client/overlay.js] (webpack)-dev-server/client/overlay.js 3.51 KiB {jsoneditor} [built] [./node_modules/webpack-dev-server/client/socket.js] (webpack)-dev-server/client/socket.js 1.53 KiB {jsoneditor} [built] [./node_modules/webpack-dev-server/client/utils/createSocketUrl.js] (webpack)-dev-server/client/utils/createSocketUrl.js 2.85 KiB {jsoneditor} [built] [./node_modules/webpack-dev-server/client/utils/log.js] (webpack)-dev-server/client/utils/log.js 964 bytes {jsoneditor} [built] [./node_modules/webpack-dev-server/client/utils/reloadApp.js] (webpack)-dev-server/client/utils/reloadApp.js 1.59 KiB {jsoneditor} [built] [./node_modules/webpack-dev-server/client/utils/sendMessage.js] (webpack)-dev-server/client/utils/sendMessage.js 402 bytes {jsoneditor} [built] [./node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 472 bytes {jsoneditor} [built] [./node_modules/webpack/hot sync ^./log$] (webpack)/hot sync nonrecursive ^./log$ 170 bytes {jsoneditor} [built] [./src/core.js] 27.7 KiB {jsoneditor} [built] [./src/defaults.js] 16.8 KiB {jsoneditor} [built] [./src/editor.js] 19.2 KiB {jsoneditor} [built] [./src/editors/ace.js] 2.91 KiB {jsoneditor} [built] + 98 hidden modules i 「wdm」: Compiled successfully.

I’m assuming it should work similar to grunt watch, but no files are generated or updated in the dist folder when I make modifications to the source files in /src. But I can see saving triggers the Webpack server to recompile.

Version: webpack 4.39.1 Time: 177ms Built at: 2019-08-24 15:15:37 Asset Size Chunks Chunk Names jsoneditor.js 2.09 MiB jsoneditor [emitted] jsoneditor Entrypoint jsoneditor = jsoneditor.js [./src/editors/string.js] 10.2 KiB {jsoneditor} [built] + 112 hidden modules i 「wdm」: Compiled successfully.

(npm run build and npm run build.dev works.)

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:18 (9 by maintainers)

github_iconTop GitHub Comments

2reactions
sirockincommented, Aug 27, 2019

I’m worried we’re producing a plethora of builds and scripts for use cases that I don’t really understand.

Here’s what I propose:

I will rename all the start scripts to debug.

I will then create a new start script that builds nonmin in watch mode but doesn’t serve the output - I think I’m right in thinking that’s how the old start script works.

If that doesn’t work for you maybe it would be better if you submit a PR with it setup exactly how you want it.

0reactions
sirockincommented, Aug 28, 2019

@pmk65 I’ve just merged latest updates to #498. Please could you close this when you’re happy?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Webpack - npm run start and build doesn't work?
I am new to webpack and i can't figure out where the problem is, i think i have installed all files and configurations...
Read more >
Improving Development with a Live Development Server
We'll start by installing webpack-dev-server with npm. Navigate to the root of the Shape Tracker directory and run the following command.
Read more >
Webpack doesn't output bundle.js (Example) - Treehouse
I started the webpack along with the video with: npm install command, But there is no bundle.js file in the directory. The webpack.config.js ......
Read more >
DevServer - webpack
webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable...
Read more >
webpack Tutorial: How to Set Up webpack 5 From Scratch
We'll begin creating the config files now. Basic configuration. Let's start setting up a Webpack build. Create a webpack.config.js in the root ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found