-
Notifications
You must be signed in to change notification settings - Fork 251
build(deps): update package.json to lerna@8
#11503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
e89ffe8
f02303a
0708d81
59f4b7e
3a7318b
fd6131f
461b050
e5dbd25
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,6 +14,5 @@ | |
| "packages/wallet/*" | ||
| ], | ||
| "rejectCycles": true, | ||
| "useWorkspaces": true, | ||
| "version": "independent" | ||
| } | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -28,8 +28,8 @@ | |
| "test:xs": "exit 0" | ||
| }, | ||
| "dependencies": { | ||
| "@agoric/internal": "^0.3.2", | ||
| "@agoric/xsnap-lockdown": "^0.14.0", | ||
| "@agoric/internal": "workspace:*", | ||
| "@agoric/xsnap-lockdown": "workspace:*", | ||
| "@endo/bundle-source": "^4.1.2", | ||
| "@endo/errors": "^1.2.13", | ||
| "@endo/eventual-send": "^1.3.4", | ||
|
|
@@ -53,15 +53,15 @@ | |
| "LICENSE*", | ||
| "api.js", | ||
| "build.env", | ||
| "moddable/modules/data", | ||
| "moddable/xs/includes", | ||
| "moddable/xs/makefiles", | ||
| "moddable/modules/data/**", | ||
| "moddable/xs/includes/**", | ||
| "moddable/xs/makefiles/**", | ||
| "moddable/xs/sources/**", | ||
|
Comment on lines
+56
to
+59
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Interesting. This is apropos of Lerna? Npm pack was forgiving.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, when testing the viability of the packages, I noticed the missing files from these subtrees. I think this was fixed a few times by other PRs that never merged.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we had some tool / script somewhere allowing us to check if there were any differences in files included in an npm package. I'm really curious why this would now have changed. |
||
| "moddable/xs/platforms/*.h", | ||
| "moddable/xs/sources", | ||
| "scripts", | ||
| "src", | ||
| "xsnap-native/xsnap/makefiles", | ||
| "xsnap-native/xsnap/sources" | ||
| "scripts/**", | ||
| "src/**", | ||
| "xsnap-native/xsnap/makefiles/**", | ||
| "xsnap-native/xsnap/sources/**" | ||
| ], | ||
| "publishConfig": { | ||
| "access": "public" | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,8 +12,8 @@ import test from 'ava'; | |
| test('pack and install xsnap', async t => { | ||
| const tmp = await mkdtemp(join(tmpdir(), 'xsnap-')); | ||
| t.teardown(() => rm(tmp, { recursive: true })); | ||
| const { stdout: npmout } = await $`npm pack --json`; | ||
| const [{ filename }] = JSON.parse(npmout); | ||
| const filename = join(tmp, 'package.tgz'); | ||
| await $`yarn pack --out ${filename}`; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, because
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 👍 |
||
| await $({ cwd: tmp })`tar xvf ${resolve(filename)}`; | ||
| await $({ cwd: join(tmp, 'package') })`npm install`; | ||
| t.pass(); | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the behavior of the new lerna regarding pre-releases? We are using pre-releases tags currently both for
devpackages and for our "release" versions.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do have a test that verifies that
npm packworks. That test switched to usingyarn packin this change, which probably accounts for the difference in requirements. Presumably,lernadrivesyarn pack.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think what
packcommand we uses changes anything to my question, which was specifically how lerna generated the new version depending on whether it was a pre-release or not. Seeing #11655, in lerna 8, the semantics of bumping version for 0.x were dependent on whether it was a pre-release or not, which seems misguided.