-
Notifications
You must be signed in to change notification settings - Fork 47.4k
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
Bug: @license
header in React 18 bundles contains vundefined
#22988
Comments
Andarist
added
the
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
label
Dec 19, 2021
bvaughn
added
Component: Build Infrastructure
and removed
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
labels
Dec 19, 2021
@Andarist The build scripts were refactored a couple of months ago to remove a One quick fix might be to just update |
I'll take it. |
zhengjitf
pushed a commit
to zhengjitf/react
that referenced
this issue
Apr 15, 2022
…s vundefined (facebook#23004) * Fix Bug: @license header in React 18 bundles contains vundefined * Remove React version from the header comment
nevilm-lt
pushed a commit
to nevilm-lt/react
that referenced
this issue
Apr 22, 2022
…s vundefined (facebook#23004) * Fix Bug: @license header in React 18 bundles contains vundefined * Remove React version from the header comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can be checked on top of the files here:
I've wanted to fix this quickly... but it turns out that your whole build pipeline is a little bit convoluted so it ain't a 5 min fix. I could still work on this but I would need some pointers as to what is the preferred fix.
From what I understand - this broken version is read here:
react/scripts/rollup/wrappers.js
Line 6 in ceee524
but the root package.json doesn't contain a version. It seems that scripts are updating "root" package.json here:
react/scripts/release/utils.js
Lines 231 to 238 in ceee524
but this only happens for the temp dir created during the release as 2 scripts are using
copyRepoToTempDirectory
.I think the scripts should be run in the context of those temp dirs and that could potentially fix the problem (maybe they already are but something else is broken? I didn't yet confirm this).
The additional problem is that this wouldn't fix the local
yarn build
as this doesn't update this root package.json version at all.The text was updated successfully, but these errors were encountered: