Closed XionWCFM closed 1 week ago
Latest commit: 24dd2385929e383343fb7e67cd44b9a7364bba05
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
suspensive.org | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 13, 2024 7:06pm |
v1.suspensive.org | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 13, 2024 7:06pm |
visualization.suspensive.org | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 13, 2024 7:06pm |
@XionWCFM is attempting to deploy a commit to the Toss Team on Vercel.
A member of the Team first needs to authorize it.
Comparing XionWCFM:rnsetup
(24dd238) with main
(ed96eea)
:warning: No benchmarks were detected in both the base of the PR and the PR.
@XionWCFM Could you resolve https://github.com/toss/suspensive/actions/runs/11814909318/job/32915046140?pr=1352 this ci error please?
In my other projects, when I set hoisted, a problem occurred in another next15
Please understand that we may create a few more commits for testing in CI.
Could you please run a workflow for this commit? @manudeli
If this commit doesn't work, you may have to use the hacky solution I originally suggested for CI.
(use a different .npmrc locally only)
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 71.86%. Comparing base (
ed96eea
) to head (24dd238
).
Overview
Configure an environment to run React Native Playground.
Guide
Test
built the entire project and confirmed that it was built without a problem.
Trouble Shooting
React Native is sensitive to cache and nodemodule state.
If it doesn't work well, delete the entire nodemodules and cache folders in the project and try again.
ETC
I realized that public-hoist-pattern[]=* is not the same as node-linker=hoisted, but rather the same as setting shamefully-hoist to true.
I set node-linker=hoisted in another project and experienced next15's build failing during the CI process.
By default, pnpm manages dependencies strictly so that only specified dependencies are used.
However, if you set this setting, you will give up strict dependency management and manage dependencies similar to the method of older generation package managers such as yarn and npm.
Should we give up the functionality of pnpm? I wish there was another way to solve this problem.
I think I can use it until I find another way. shamefully-hoist and public-hoist-pattern[]=*