monorepo

问题 I have a large node.js monorepo with several applications and packages and inter dependencies. It is all managed with yarn workspaces and a little bit of lerna. Everything works great for me, however I am having trouble trying to deploy one of the applications in this monorepo to google app engine. The main issue is that the app engine wants to install packages that are located only locally and are not on npm, and it throws an error. I've scoured the google cloud documentations but did not

问题 I am using yarn workspaces to create monorepo for react and react-native . I tried to add redux to @app/common and it works fine with react , but it is not resolving in native. You can see the source at https://github.com/Faisal-Manzer/react-and-react-native-monorepo/tree/08-redux. When loading bundle it is giving the following error. error: Error: Unable to resolve module `redux` from `../common/reducers/index.js`: redux could not be found within the project or in these directories: ../..

问题 Further outlining is in the context of NodeJS and Monorepo (based on Lerna). I have AWS stack with several AWS Lambda inside deployed by means of AWS CloudFormation. Some of the lambdas are simple (the single small module) and could be inlined: https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-lambda.Code.html#static-from-wbr-inlinecode const someLambda = new Function(this, 'some-lambda', { code: Code.fromInline(fs.readFileSync(require.resolve(<relative path to lambda module>),

问题 Further outlining is in the context of NodeJS and Monorepo (based on Lerna). I have AWS stack with several AWS Lambda inside deployed by means of AWS CloudFormation. Some of the lambdas are simple (the single small module) and could be inlined: https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-lambda.Code.html#static-from-wbr-inlinecode const someLambda = new Function(this, 'some-lambda', { code: Code.fromInline(fs.readFileSync(require.resolve(<relative path to lambda module>),

来源： https://stackoverflow.com/questions/60180630/lerna-always-lists-all-packages-ready-to-publish-when-running-workflow-of-github

来源： https://stackoverflow.com/questions/60180630/lerna-always-lists-all-packages-ready-to-publish-when-running-workflow-of-github

来源： https://stackoverflow.com/questions/60180630/lerna-always-lists-all-packages-ready-to-publish-when-running-workflow-of-github

问题 Working on a larger typescript project we decided to move the code to a monorepo with yarn workspaces . We use webpack to build and bundle and everything works well (especially the linking between local modules/packages). Since yarn workspaces will store most of the node_modules in the mono repo's root folder, the IDE (IntelliJ as well as VSCode) have problems resolving the imports to any node_modules when coding inside a "inner" project (so called "package" of a monorepo). The strange thing

问题 We're starting to adopt a monorepo setup using yarn workspaces and we'd like to have our firebase functions inside it. The repo structure is something like: repo node_modules <- all dependencies packages core commom functions <- firebase functions So, I have 2 problems with this setup: The dependencies of the functions don't live on the same folder as the entry file from functions The functions depends on other packages such as core and commom that are in the repo so yarn symlinks from node

问题 I have a monorepo that has many micro-services in it. There are some library-type functions / classes that I want to make available to any micro-service that needs it. However, if that library package declares a peer dependency, the peer dependency is not found when running code from within the thing that depends on the library. Consider this repo structure: lib some-library (peerDepends on foo ) index.js (requires foo ) node_modules will be empty services some-service (depends on foo , and