You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 22, 2024. It is now read-only.
Warning: patch-package detected a patch file version mismatch
Don't worry! This is probably fine. The patch was still applied
successfully. Here's the deets:
Patch file created for [email protected]
applied to [email protected]
At path
node_modules/antd
This warning is just to give you a heads-up. There is a small chance of
breakage even though the patch was applied successfully. Make sure the package
still behaves like you expect (you wrote tests, right?) and then run
patch-package antd
to update the version in the patch file name and make this warning go away.
Warning: patch-package detected a patch file version mismatch
Don't worry! This is probably fine. The patch was still applied
successfully. Here's the deets:
Patch file created for [email protected]
applied to [email protected]
At path
node_modules/fb-watchman
This warning is just to give you a heads-up. There is a small chance of
breakage even though the patch was applied successfully. Make sure the package
still behaves like you expect (you wrote tests, right?) and then run
patch-package fb-watchman
to update the version in the patch file name and make this warning go away.
Warning: patch-package detected a patch file version mismatch
Don't worry! This is probably fine. The patch was still applied
successfully. Here's the deets:
Patch file created for [email protected]
applied to [email protected]
At path
node_modules/metro
This warning is just to give you a heads-up. There is a small chance of
breakage even though the patch was applied successfully. Make sure the package
still behaves like you expect (you wrote tests, right?) and then run
patch-package metro
to update the version in the patch file name and make this warning go away.
Warning: patch-package detected a patch file version mismatch
Don't worry! This is probably fine. The patch was still applied
successfully. Here's the deets:
Patch file created for [email protected]
applied to [email protected]
At path
node_modules/metro-runtime
This warning is just to give you a heads-up. There is a small chance of
breakage even though the patch was applied successfully. Make sure the package
still behaves like you expect (you wrote tests, right?) and then run
patch-package metro-runtime
to update the version in the patch file name and make this warning go away.
ERROR Failed to apply patch for package @emotion/cache at path
node_modules/@emotion/cache
This error was caused because @emotion/cache has changed since you
made the patch file for it. This introduced conflicts with your patch,
just like a merge conflict in Git when separate incompatible changes are
made to the same piece of code.
Maybe this means your patch file is no longer necessary, in which case
hooray! Just delete it!
Otherwise, you need to generate a new patch file.
To generate a new one, just repeat the steps you made to generate the first
one.
i.e. manually make the appropriate file changes, then run
patch-package @emotion/cache
Info:
Patch file: patches/@emotion+cache+11.7.1.patch
Patch was made for version: 11.7.1
Installed version: 11.11.0
patch-package finished with 4 warning(s), 1 error(s).
yarn install v1.22.22
[1/4] Resolving packages...
success Already up-to-date.
$ cd .. && ./ts-node ./plugins/postinstall.tsx
Done in 1.02s.
yarn run v1.22.22
$ /home/hugo/software/flipper/desktop/node_modules/.bin/tsc -b pkg-lib/tsconfig.json
Done in 0.34s.
yarn run v1.22.22
$ tsc -b tsc-root/tsconfig.json && ./ts-node ./scripts/compute-package-checksum.tsx -d ./babel-transformer -o ./lib/checksum.txt
error TS2688: Cannot find type definition file for 'react-dom/next'.
The file is in the program because:
Entry point of type library 'react-dom/next' specified in compilerOptions
flipper-plugin/tsconfig.json:11:7
11 "react-dom/next"
~~~~~~~~~~~~~~~~
File is entry point of type library specified here.
Found 1 error.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
🐛 Bug Report
full info:
arn install v1.22.22
$ node scripts/prepare-watchman-config.js && yarn config set ignore-engines
yarn config v1.22.22
success Set "ignore-engines" to true.
Done in 0.05s.
[1/4] Resolving packages...
success Already up-to-date.
$ patch-package && yarn --cwd plugins install --mutex network:30331 && yarn tsc -b pkg-lib/tsconfig.json && ./ts-node scripts/remove-plugin-entry-points.tsx && yarn build:tsc && yarn build:themes
patch-package 6.5.1
Applying patches...
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
Warning: patch-package detected a patch file version mismatch
Don't worry! This is probably fine. The patch was still applied
successfully. Here's the deets:
Patch file created for
[email protected]
applied to
[email protected]
At path
node_modules/antd
This warning is just to give you a heads-up. There is a small chance of
breakage even though the patch was applied successfully. Make sure the package
still behaves like you expect (you wrote tests, right?) and then run
patch-package antd
to update the version in the patch file name and make this warning go away.
Warning: patch-package detected a patch file version mismatch
Don't worry! This is probably fine. The patch was still applied
successfully. Here's the deets:
Patch file created for
[email protected]
applied to
[email protected]
At path
node_modules/fb-watchman
This warning is just to give you a heads-up. There is a small chance of
breakage even though the patch was applied successfully. Make sure the package
still behaves like you expect (you wrote tests, right?) and then run
patch-package fb-watchman
to update the version in the patch file name and make this warning go away.
Warning: patch-package detected a patch file version mismatch
Don't worry! This is probably fine. The patch was still applied
successfully. Here's the deets:
Patch file created for
[email protected]
applied to
[email protected]
At path
node_modules/metro
This warning is just to give you a heads-up. There is a small chance of
breakage even though the patch was applied successfully. Make sure the package
still behaves like you expect (you wrote tests, right?) and then run
patch-package metro
to update the version in the patch file name and make this warning go away.
Warning: patch-package detected a patch file version mismatch
Don't worry! This is probably fine. The patch was still applied
successfully. Here's the deets:
Patch file created for
[email protected]
applied to
[email protected]
At path
node_modules/metro-runtime
This warning is just to give you a heads-up. There is a small chance of
breakage even though the patch was applied successfully. Make sure the package
still behaves like you expect (you wrote tests, right?) and then run
patch-package metro-runtime
to update the version in the patch file name and make this warning go away.
ERROR Failed to apply patch for package @emotion/cache at path
node_modules/@emotion/cache
This error was caused because @emotion/cache has changed since you
made the patch file for it. This introduced conflicts with your patch,
just like a merge conflict in Git when separate incompatible changes are
made to the same piece of code.
Maybe this means your patch file is no longer necessary, in which case
hooray! Just delete it!
Otherwise, you need to generate a new patch file.
To generate a new one, just repeat the steps you made to generate the first
one.
i.e. manually make the appropriate file changes, then run
patch-package @emotion/cache
Info:
Patch file: patches/@emotion+cache+11.7.1.patch
Patch was made for version: 11.7.1
Installed version: 11.11.0
patch-package finished with 4 warning(s), 1 error(s).
yarn install v1.22.22
[1/4] Resolving packages...
success Already up-to-date.
$ cd .. && ./ts-node ./plugins/postinstall.tsx
Done in 1.02s.
yarn run v1.22.22
$ /home/hugo/software/flipper/desktop/node_modules/.bin/tsc -b pkg-lib/tsconfig.json
Done in 0.34s.
yarn run v1.22.22
$ tsc -b tsc-root/tsconfig.json && ./ts-node ./scripts/compute-package-checksum.tsx -d ./babel-transformer -o ./lib/checksum.txt
error TS2688: Cannot find type definition file for 'react-dom/next'.
The file is in the program because:
Entry point of type library 'react-dom/next' specified in compilerOptions
flipper-plugin/tsconfig.json:11:7
11 "react-dom/next"
~~~~~~~~~~~~~~~~
File is entry point of type library specified here.
Found 1 error.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Environment
OS:Ubuntu 24.04 LTS
Windowing System:Wayland
GNOME version:46
The text was updated successfully, but these errors were encountered: