Skip to content

chore: Prep for dependabot #242

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

Merged
merged 2 commits into from
Feb 18, 2020
Merged

chore: Prep for dependabot #242

merged 2 commits into from
Feb 18, 2020

Conversation

seebees
Copy link
Contributor

@seebees seebees commented Feb 9, 2020

lerna link convert

This links all the packages to the root
and removed the need for lerna bootstrap
This moves all the devDependencies from the individual
package.json files to the root,
and links the internal modules together.
This does make things complicated
for integration-browser and integration-node
because these files compile the TS to JS for a CLI.
But this JS file does not exists because it is build from the Typescript.
So there is a chicken/egg situation where the file needs to exists to be installed,
but the file needs to be built.
I added a hack to touch the file when the monorepo is built.

This should help with dependabot PRs
as well as making npm audit just work.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Check any applicable:

  • Were any files moved? Moving files changes their URL, which breaks all hyperlinks to the files.

`lerna link convert`

This links all the packages to the root
and removed the need for `lerna bootstrap`
This moves all the `devDependencies` from the individual
`package.json` files to the root,
and links the internal modules together.
This does make things complicated
for `integration-browser` and `integration-node`
because these files compile the TS to JS for a CLI.
But this JS file does not exists because it is build from the Typescript.
So there is a chicken/egg situation where the file needs to exists to be installed,
but the file needs to be built.
I added a hack to `touch` the file when the monorepo is built.

This should help with dependabot PRs
as well as making `npm audit` just work.
@seebees seebees requested a review from a team February 14, 2020 23:43
@seebees seebees merged commit 4d8974c into aws:master Feb 18, 2020
@seebees seebees deleted the dependabot branch February 18, 2020 02:06
seebees added a commit to seebees/aws-encryption-sdk-javascript that referenced this pull request Apr 1, 2020
This is an explicit update to versions.
Additionally all sub modules package-lock.json files are removed.

When `lerna link` was run, in aws#242
all modules were linked together at the root.
This means that the root package-lock.json file is responsible
for all sub modules state.
Lerna does not maintain the state on these modules package-lock.json anymore.
So this information is redundant.

Finaly, update `local_verdaccio_publish`
to not reset package-lock.json files as they do not exist.
seebees added a commit to seebees/aws-encryption-sdk-javascript that referenced this pull request Apr 1, 2020
This is an explicit update to versions.
Additionally all sub modules package-lock.json files are removed.

When `lerna link` was run, in aws#242
all modules were linked together at the root.
This means that the root package-lock.json file is responsible
for all sub modules state.
Lerna does not maintain the state on these modules package-lock.json anymore.
So this information is redundant.

Finally, update `local_verdaccio_publish`
to not reset package-lock.json files as they do not exist.
@seebees seebees mentioned this pull request Apr 1, 2020
1 task
seebees added a commit that referenced this pull request Apr 1, 2020
This is an explicit update to versions.
Additionally all sub modules package-lock.json files are removed.

When `lerna link` was run, in #242
all modules were linked together at the root.
This means that the root package-lock.json file is responsible
for all sub modules state.
Lerna does not maintain the state on these modules package-lock.json anymore.
So this information is redundant.

Finally, update `local_verdaccio_publish`
to not reset package-lock.json files as they do not exist.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants