
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
@lerna-lite/init
Advanced tools
Lerna-Lite init commmand - Create a new Lerna repo or upgrade an existing repo to the current version of Lerna
lerna init
) - Init command 🛠️Create/initialize a new Lerna-Lite repo or upgrade an existing repo to the current version of Lerna-Lite CLI
npm install @lerna-lite/cli -D -W
# then use it (see usage below)
lerna init
# OR use npx
npx lerna init
$ lerna init
Create/initialize a new Lerna-Lite repo or upgrade an existing repo to the current version of Lerna-Lite.
Lerna assumes the repo has already been initialized with
git init
.
When run, this command will:
lerna
as a devDependency
in package.json
if it doesn't already exist.lerna.json
config file to store the version
number and also add a packages
property (unless you have --use-workspaces)
lerna.json
file, you can read the lerna.json Wiki.Example output on a new git repo:
$ lerna init
lerna info version v1.3.0
lerna info Updating package.json
lerna info Creating lerna.json
lerna success Initialized Lerna files
lerna.json
{
"version": "0.0.0",
"packages": ["packages/*"]
}
--independent
$ lerna init --independent
This flag tells Lerna-Lite to use independent versioning mode.
--exact
$ lerna init --exact
By default, lerna init
will use a caret range when adding or updating
the local version of lerna
, just like npm install --save-dev lerna
.
To retain the lerna
of "exact" comparison, pass this flag.
It will configure lerna.json
to enforce exact match for all subsequent executions.
{
"command": {
"init": {
"exact": true
}
},
"version": "0.0.0"
}
--use-workspaces
$ lerna init --use-workspaces
This flag tells Lerna-Lite to add a workspaces
property in the project root package.json
instead of the default lerna.json
file, which is the workspace setup that Yarn/NPM now use
Note: pnpm users should not use this flag, they should simply use the default which is to have packages
in lerna.json
file (as shown in default usage lerna.json
config).
lerna.json
{
"version": "0.0.0"
}
package.json
(project root){
"name": "monorepo",
"devDependencies": {
"@lerna-lite/cli": "^1.0.0"
},
"workspaces": ["packages/*"]
}
FAQs
Lerna-Lite init commmand - Create a new Lerna repo or upgrade an existing repo to the current version of Lerna
We found that @lerna-lite/init demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.