Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webpack build error with node---UnhandledPromiseRejectionWarning #16785

Closed
CodeMagic6 opened this issue Nov 6, 2017 · 1 comment
Closed

webpack build error with node---UnhandledPromiseRejectionWarning #16785

CodeMagic6 opened this issue Nov 6, 2017 · 1 comment
Labels
errors Issues and PRs related to JavaScript errors originated in Node.js core. promises Issues and PRs related to ECMAScript promises. question Issues that look for answers.

Comments

@CodeMagic6
Copy link

CodeMagic6 commented Nov 6, 2017

node-version: 7.6.0 and 8.9.0
platform: windows10

Recently when I use webpack command 'npm run build' It shows Bugs but It's OK few days ago.below it's the message.

(node:7948) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: original.line and original.column are not numbers -- you probably meant to omit the original mapping entirely and only map the generated position. If so, pass null for the original mapping instead of an object with empty or null values.
(node:7948) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@benjamingr
Copy link
Member

Hey, sorry for the confusing message! I've actually raised an issue about better naming it yesterday and we'll make those errors clearer.

The actual error is:

Error: original.line and original.column are not numbers -- you probably meant to omit the original mapping entirely and only map the generated position. If so, pass null for the original mapping instead of an object with empty or null values.

This is a webpack error (and not a Node.js error) - specifically you're not passing the source maps options correctly or are using a plugin that isn't doing so. Feel free to open an issue in StackOverflow or in https://github.com/nodejs/help or in Webpack's official support channels.

This issue tracker is about suggestions for improvements or bugs in Node.js itself - this isn't one so I'm going to go ahead and close it.

If you're unsure who to approach about this issue please feel free to leave a comment and I'll try to work with you and get you more support from the webpack team or relevant plugin authors - although I warmly recommend StackOverflow from personal experience (if you create a mcve first it works best).

Thanks for raising the issue :)

@benjamingr benjamingr added errors Issues and PRs related to JavaScript errors originated in Node.js core. promises Issues and PRs related to ECMAScript promises. question Issues that look for answers. labels Nov 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
errors Issues and PRs related to JavaScript errors originated in Node.js core. promises Issues and PRs related to ECMAScript promises. question Issues that look for answers.
Projects
None yet
Development

No branches or pull requests

2 participants