-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
UnhandledPromiseRejectionWarning when building. #11
Comments
Confirming this happens to me as well. Node 9.1.0 |
hmm, is this node 9 specific? I've tested against node 8 so far. |
Happens to me in both 8 and 9.
…On Tue, 5 Dec 2017, 20.58 Devon Govett, ***@***.***> wrote:
hmm, is this node 9 specific? I've tested against node 8 so far.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAtB7XdvEgBfcGop83_v38GthMB2mz1Fks5s9aBSgaJpZM4Q23fJ>
.
|
Same here. I just followed get-started guide as it failed. 😢
Error
Steps to reproduce:// module.js
export function helloWorld () {console.log('Hello World!');}; // index.js
import { helloWorld } from './module';
helloWorld(); <script src="index.js"></script> Command
|
I followed the getting started and had the same results. Sample repo here: https://github.com/mwarger/parcel-getting-started-windows Windows 10
|
This happens even with the simplest html file and no JS involved: <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta http-equiv="X-UA-Compatible" content="ie=edge">
<title>Test</title>
</head>
<body>
<div id="app"/>
</body>
</html>
|
I get the same error. When I try to do a build on the Windows subsystem for Linux, the error goes away (but I get a new one, related: #8)
So it does appear to be a Windows issue. For people on Windows, WSL seems like a workaround for the time being. I got it to build with the |
hmm, seems like a windows issue 😢? I can try to setup a vm to test, but would be great if someone could dig into this a bit and get more info on the errors being logged there (e.g. what promise is being rejected, etc.). Thanks in advance for your help! 😄 |
@devongovett It turns out that src/utils/config.js#L6 got recursively calling itself, which causes Maximum call stack size exceeded. Not find out how to solve it yet. test/css.js#L8 in let b = await bundle(__dirname + '/integration/css/index.js'); src/Bundler.js#L275 in processed = await this.farm.run(asset.name, asset.package, this.options); src/WorkerFarm.js#L63 in return this.localWorker.run(...args); src/worker.js#L20 in await asset.process(); src/assets/JSAsset.js#L72 in await babel(this); src/transforms/babel.js#L39 in let babelrc = await config.resolve(asset.name, ['.babelrc', '.babelrc.js']); src/utils/config.js#L25 in return resolve(filepath, filenames, root); |
resolve(filepath, filenames, root); Let's look at the return value in Windows and Mac environments. This is windows screenshot |
In src/utils/config.js#L10, I did:
|
It's probably that |
@thejameskyle exactly, I created a PR #48 which fix it but test are still failing. We should integrate CI. |
Same for node v7.9.0, win10 x64, parcel 1.2 |
when we can use the version 1.0.3 ? |
Published v1.0.3. |
Just for what it's worth I got this exact same error trying parcel on MacOS High Sierra with a minimum HTML page and Node 6x latest. Looks like Parcel requires >= 8x, as switching from Boron to Carbon fixed it. Would probably be worth noting this on the docs, as I couldn't find anything indicating which version of Node was required. |
same issue here with
----- updates: -----
and it worked for me when i removed |
Enable workerize * Use unique keys in all workerize assets and do not process node_modules * Configure workerize transformer * Inline workerize workers * Add transformer to config package.json Approved-by: Will Binns-Smith
Merge v2 2021-01-05 Approved-by: Gora Kong Approved-by: Agnieszka Gawrys
Hi. As many others I am very excited for the work you are doing here. Badly needed.
I have stumpled upon a slight problem building even just the simplest html file:
After running parcel index.html, the "dist" folder is created but it is empty.
The following is the console errors:
The text was updated successfully, but these errors were encountered: