lerna.json
See original GitHub issueAdding configuration and state to repos through CLI flags and separate files is going to get crazy. We should have one place for all of this in a repo.
{
"version": "1.0.0",
"independent": false,
"owners": [
"kittens",
"thejameskyle",
"hzoo"
],
// ...
}
Issue Analytics
- State:
- Created 8 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Lerna is a fast, modern build system for managing ... - GitHub
Lerna is a fast modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
Read more >Lerna: Documentation
Lerna is a fast modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
Read more >How To Manage Monorepos With Lerna - DigitalOcean
Lerna is as a tool for managing JavaScript projects with multiple packages with features ... The init command creates a lerna.json file.
Read more >Setting up a monorepo with Lerna for a TypeScript project
json is a Lerna configuration file. package.json is our usual manifest file. { "packages" ...
Read more >JavaScript Monorepos with Lerna - Semaphore CI
Move all your applications, libraries, subprojects, and shared code into the packages folder. Each project should have a package.json and, ...
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 you go the package.json route, I would suggest namespacing it under
lerna
or somesuch, analogous to the way babel and eslint (and others) do it.It could also just work on top of the package.json