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
As a developer working with a monorepo containing approximately 20 React Native projects,
Because react-native scripts and bundler assumed the dependent modules reside under the application's node_modules folder during installation and runtime,
With yarn I use nohoist config
{ "nohoist": ["**/*"] }
With pnpm I use shamefully-hoist but it only symlink direct dependencies of each project (workspace),
Describe the solution you'd like
I want an option to symlink all depth level (both direct and non-direct dependencies) to project (workspace) level node_modules.
Describe the drawbacks of your solution
Installation time will be increased when this options was set because it will be find all depth dependencies and symlink them all to project (workspace) level node_modules
Describe alternatives you've considered
Because react-native scripts and bundler assumed the native dependent modules reside under the application's node_modules folder during installation and runtime
So I collect error after bundle about the native dependencies and push them all to optionalDependencies of target workspace package.json. That make them to be direct dependencies. Then it could be symlinked to target workspace level node_modules.
The text was updated successfully, but these errors were encountered:
Contribution
Describe the user story
As a developer working with a monorepo containing approximately 20 React Native projects,
Because react-native scripts and bundler assumed the dependent modules reside under the application's node_modules folder during installation and runtime,
With yarn I use nohoist config
With pnpm I use
shamefully-hoist
but it only symlink direct dependencies of each project (workspace),Describe the solution you'd like
I want an option to symlink all depth level (both direct and non-direct dependencies) to project (workspace) level node_modules.
Describe the drawbacks of your solution
Installation time will be increased when this options was set because it will be find all depth dependencies and symlink them all to project (workspace) level node_modules
Describe alternatives you've considered
Because react-native scripts and bundler assumed the native dependent modules reside under the application's node_modules folder during installation and runtime
So I collect error after bundle about the native dependencies and push them all to
optionalDependencies
of target workspace package.json. That make them to be direct dependencies. Then it could be symlinked to target workspace level node_modules.The text was updated successfully, but these errors were encountered: