Skip to content

npm: update dependencies #21

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.

Sign up for GitHub

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 9 commits into from
Feb 11, 2022
Merged

npm: update dependencies #21

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
19356f8
npm: regenerate package-lock.json for npm v7+
Totktonada Feb 10, 2022
9f0f0d9
npm/security: update node-fetch (2.6.1 -> 2.6.7)
Totktonada Feb 10, 2022
214ae73
npm: update @zeit/ncc@0.22.3 to @vercel/ncc@0.33.1
Totktonada Feb 10, 2022
b199c43
npm: update dependencies to latest compatible ones
Totktonada Feb 10, 2022
c39ebcc
build: validate that an error is of type Error
Totktonada Feb 10, 2022
320bb3f
build: regenerate index.js
Totktonada Feb 10, 2022
936712a
doc: add hints for contributors
Totktonada Feb 10, 2022
fbbee14
gitignore: add Vim Swap files
Totktonada Feb 10, 2022
b5a4176
ci: drop ubuntu-16.04
Totktonada Feb 11, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
npm: regenerate package-lock.json for npm v7+ 
I had intention to install locked dependencies and called `npm install`
in the project directory first time. Surprisingly, it updates my
`package-lock.json` with `lockfileVersion: 2` (was 1) and the new
`packages` field.

The documentation [1] says that it is the new lock file format for npm
v7+, which is compatible with npm v6. Okay, let's move to the new
format.

FWIW, my versions are the following:

| Package | Version |
| ------- | ------- |
| nodejs  | 16.13.1 |
| npm     | 8.1.2   |

[1]: https://docs.npmjs.com/cli/v8/configuring-npm/package-lock-json
  • Loading branch information
@Totktonada
Totktonada committed Feb 10, 2022
commit 19356f8ee7453d40faf40525eeaaa3001bcffc85
Loading