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
When I read the lerna documentation for the first time, I thought loc should be a path. But the absolute path is too long, so I used a relative path. As a result, it will always be created in the fist package directory.
I have two packages directories in lerna.json :
"packages": [
"apps/*",
"libs/*"
],
Expected Behavior
when I run command lerna create core ./libs, I would want to create a new package in the libs/ directory.
Current Behavior
Using lerna create, the package keeps creating in apps/ directory.
Location current supports absolute path and packageName, I think it should support relative path too, eg lerna create core ./libs or warn right location format.
"packages": [
"apps/*",
"libs/*"
],
Your Environment
Executable
Version
lerna --version
4.0.0
npm --version
7.21.1
yarn --version
1.22.10
node --version
v16.8.0
OS
Version
macOS Big Sur
11.2.3
The text was updated successfully, but these errors were encountered:
boyan1010
changed the title
lerna create <pkg> [loc], loc can use relative path to create package or warn right formatlerna create <pkg> [loc], can use relative path to create package or warn right format
Aug 28, 2021
can use relative path to create package
When I read the lerna documentation for the first time, I thought loc should be a path. But the absolute path is too long, so I used a relative path. As a result, it will always be created in the fist package directory.
I have two packages directories in lerna.json :
Expected Behavior
when I run command
lerna create core ./libs
, I would want to create a new package in the libs/ directory.Current Behavior
Using lerna create, the package keeps creating in apps/ directory.
before run command
run command
lerna create core ./libs
Possible Solution
Location current supports absolute path and packageName, I think it should support relative path too, eg
lerna create core ./libs
or warn right location format.Your Environment
lerna --version
npm --version
yarn --version
node --version
The text was updated successfully, but these errors were encountered: