-
-
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segfault introduced in 2.9.0 #9670
Comments
Also feel free to ask for help if you run into any other problems (e.g. regarding configuration), for example in the Github Discussions or on Discord! |
This is apparently an infinite recursion in the resolver when resolving
|
It's actually unrelated to preact. {
"compilerOptions": {
"paths": {
"preact/compat": [
"node_modules/@types/react",
"preact/compat"
]
}
}
} includes https://unpkg.com/browse/@types/react@17.0.39/package.json |
馃悰 bug report
Heya folks, just thought I'd report there seems to be a deterministic segfault with this example repository. I've been able to reproduce this issue in every version of parcel from 2.90 to 2.12.0 (latest). I was able to reproduce this issue on Centos7 with node16.13.2, Ubuntu22.04.4 LTS with node20, and Mac OS X 14.2.1 with node16.20.2 - I'm happy to provide more information about any versions that are necessary, please let me know.
It's worth pointing out that this doesn't happen in parcel 2.8.3 - I haven't checked lower, as this version will be fine for our purposes.
Also, worth pointing out that while I did a cursory scan of previously open issues, and indeed found some closed that were related to segfaults, I couldn't find one describing this particular issue. Please feel free to close if this isn't relevant for your purposes.
馃帥 Configuration (.babelrc, package.json, cli command)
provided in link above, but will paste here as well:
package.json:
tsconfig.json:
example.tsx:
build.mjs:
(no babel config was explicitly necessary to produce the above behavior)
馃 Expected Behavior
Parcel shouldn't segfault (if something is wrong with the config, parcel should raise that up to the user).
馃槸 Current Behavior
Parcel segfaults with no additional information
馃拋 Possible Solution
none at this time
馃敠 Context
We are testing parcel for use as a javascript bundler, and wanted to prove out the utility of it and hit this (admittedly with our rather arcane tsconfig/react/preact setup). We can drop down to a lower version to continue proving out utility, so no worries there, just figured that the reproducibility here might be useful
馃捇 Code Sample
https://github.com/mpmartinez-etsy/parcel-segfault-example
馃實 Your Environment
The text was updated successfully, but these errors were encountered: