Shareable configuration on monorepo fails due to incompatible lockfiles
See original GitHub issueHi there,
Considering this directory structure:
ParentProject
package.json
.browserlistrc
...
src
packages
foo
package.json
...
How can have the project foo
have access to the .browserlistrc
resolved config from ParentProject?
EDIT:
After further investigation, we realized the root cause of this issue is that foo
project had an outdated lock file that was causing browserslist
to resolve to a different query instead of using the same dependencies that are defined in the package which contains .browserlistrc
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (7 by maintainers)
Top Results From Across the Web
Turning a Node.js Monolith into a Monorepo without ... - InfoQ
Splitting monoliths into services creates complexity in maintaining multiple repositories (one per service) with separate (yet interdependent) ...
Read more >Configuration Options - Renovate Docs
Any config you define applies to the whole repository (e.g. if you have a monorepo). You can store your Renovate configuration file in...
Read more >Yarn install failing on GitHub Actions - Stack Overflow
By default, Yarn will throw an exception on yarn install if it detects that a package doesn't match the checksum stored within the...
Read more >Why Lerna and Yarn Workspaces is a Perfect Match for ...
In short, a so-called Mono-Repo is a (git) repository that houses multiple projects. Such projects are called workspaces or packages. In ...
Read more >Advanced package manager features for npm, Yarn, and pnpm
When using the default configuration, pnpm and Yarn Berry do not use ... go wrong in a monorepo project where the hoisting algorithm...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If it is a bug, can you provide extra information to reproduce the problem? Maybe create a simple example?
I am going to sleep right now and will answer you tomorrow.
I will create a separate issue for us to further elaborate on it
Will forward this internally
I updated the title and issue description to better align with the problem