Debug breaks on current release candidate
See original GitHub issueUsing: v2.2.0-rc.0
Do you want to request a feature or report a bug?
Was originally a bug posted here but is relevant to all rc users.
If the current behavior is a bug, please provide the steps to reproduce.
There is currently an issue with the debug module which has been fixed on master but not officially released yet.
It prevents the sever from running correctly with the following output:
ERROR in ./~/debug/browser.js
Module build failed: Error: Couldn't find preset "es2015" relative to directory "/home/otis/Developer/hassle/node_modules/debug"
at /home/otis/Developer/hassle/node_modules/babel-core/lib/transformation/file/options/option-manager.js:299:19
at Array.map (native)
at OptionManager.resolvePresets (/home/otis/Developer/hassle/node_modules/babel-core/lib/transformation/file/options/option-manager.js:270:20)
at OptionManager.mergePresets (/home/otis/Developer/hassle/node_modules/babel-core/lib/transformation/file/options/option-manager.js:259:10)
at OptionManager.mergeOptions (/home/otis/Developer/hassle/node_modules/babel-core/lib/transformation/file/options/option-manager.js:244:14)
at OptionManager.init (/home/otis/Developer/hassle/node_modules/babel-core/lib/transformation/file/options/option-manager.js:374:12)
at File.initOptions (/home/otis/Developer/hassle/node_modules/babel-core/lib/transformation/file/index.js:216:65)
at new File (/home/otis/Developer/hassle/node_modules/babel-core/lib/transformation/file/index.js:139:24)
at Pipeline.transform (/home/otis/Developer/hassle/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
at transpile (/home/otis/Developer/hassle/node_modules/babel-loader/lib/index.js:38:20)
@ ./~/sockjs-client/lib/main.js 25:10-26
@ ./~/sockjs-client/lib/entry.js
@ (webpack)-dev-server/client/socket.js
@ (webpack)-dev-server/client?http://localhost:4000
@ multi main
To fix in the meantime you can add this to your package.json:
"debug": "git://github.com/visionmedia/debug#master"
What is the expected behavior?
For the server to run without breaking.
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention your webpack and Operating System version.
Using webpack v2.2.0-rc.0 and Ubuntu 16.04.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Debug build works fine, Release build breaks? - Stack Overflow
I'm getting this error when debugging a Release build: Unhandled exception at 0x55BA32F9 (Windows.UI.Xaml.dll) in AppName.exe: 0xC000027B: An ...
Read more >Troubleshoot Breakpoints in the Visual Studio Debugger
If you're debugging optimized code, make sure the function where your breakpoint is set isn't being inlined into another function. The Debugger.
Read more >Debug Node.js Apps using Visual Studio Code
The Visual Studio Code editor includes Node.js debugging support. Set breakpoints, step-in, inspect variables and more.
Read more >Troubleshooting and tips — Numba 0.50.1 documentation
Setting the debug keyword argument in the jit decorator (e.g. @jit(debug=True) ) enables the emission of debug info in the jitted code. To...
Read more >GDB: A quick guide to make your debugging easier
Debug support for optimized code is still work in progress on both GCC and CLANG, so for the best debugging experience use the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I will double check tonight when I get home but all of my other excludes have been handled like that and appear to be working, will let you know.
Hey @SpaceK33z only just got back to this today, looks like you were spot on about the
/node_modules/I have updated and everything appears to be working.Cheers.