Commit Graph

5 Commits

Author SHA1 Message Date
Richard Baker
5fa324a680 Add package-lock.json file using Node 16 LTS & NPM 8
Creates a "v2" package-lock.json file for consistent dependency
installation.

Lock file created using `npm i --package-lock-only`

Signed-off-by: Richard Baker <richard.baker@digital.cabinet-office.gov.uk>
2022-04-05 11:36:33 +01:00
Chris Hill-Scott
c11a15338c Remove package-lock.json
I don’t think we’re getting any benefit from it. Especially since we’re
not running any Node code in production, but just using it to build the
frontend.

The downside is we keep getting these massive diffs which means we don’t
get an accurate line count on pull requests.

Followed instructions here:
https://codeburst.io/disabling-package-lock-json-6be662f5b97d
2017-09-27 12:15:33 +01:00
chrisw
f012ec57c0 Allow user to add multiple reply-to addresses 2017-09-25 17:05:41 +01:00
venusbb
3a1e76ba92 Progress: passed trial_mode to /service end point 2017-09-22 15:46:52 +01:00
Chris Hill Scott
8e19dc194a Add package-lock.json to version control
`package-lock.json` is a file that newer versions of NPM generated
when installing dependencies.

> It describes the exact tree that was generated, such that
> subsequent installs are able to generate identical trees,
> regardless of intermediate dependency updates.

> This file is intended to be committed into source repositories.

– https://docs.npmjs.com/files/package-lock.json
2017-07-03 12:11:24 +01:00