Platform_Mirocod

9314 Commits

14 Branches

154 Tags

505 MiB

Tree: 7c8e116987

Commit Graph

Author	SHA1	Message	Date
silverwind	80bfd5145c	add package-lock=true in .npmrc (#9736 ) Some users (like me) have this option disabled in their global npm config which can lead to package-lock.json not being updated. This explicitely enables the option for this repo, so that the file is always updated when adding/removing dependencies. Co-authored-by: techknowlogick <matti@mdranta.net> Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com>	5 years ago
silverwind	a71cabbd53	add 'npm' and 'npm-update' make targets and lockfile (#7246 ) * add 'npm' and 'npm-update' make targets and lockfile - `make npm` installs and updates node_modules, triggered automatically on `make css` and `make js` as it completes reasonably fast and ensures consistent modules. - `make npm-update` updates all dependencies to their latest version, regenerates `node_modules` from scratch and updates `package-lock.json`. It uses npm modules `updates` written by yours truly to find the latest version of each dependency. * add suggested make dependencies * remove package-lock.json during npm-update * regenerate package-lock.json	6 years ago
silverwind	04f996f1f9	remove and disable package-lock (#6969 ) * remove and disable package-lock Using exact versions in package.json has the same effect as lockfiles without all the troubles the lockfiles bring (different versions of package manager generating different lockfiles primarily). Ensured we only use exact versions in package.json and stopped generation of new lockfiles via .npmrc which is support by both the npm and yarn package managers. Fixes: https://github.com/go-gitea/gitea/issues/6967 * enable save-exact	6 years ago

Author

SHA1

Message

Date

silverwind

80bfd5145c

add package-lock=true in .npmrc (#9736 )

Some users (like me) have this option disabled in their global npm
config which can lead to package-lock.json not being updated. This
explicitely enables the option for this repo, so that the file is
always updated when adding/removing dependencies.

Co-authored-by: techknowlogick <matti@mdranta.net>
Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com>

5 years ago

silverwind

a71cabbd53

add 'npm' and 'npm-update' make targets and lockfile (#7246 )

* add 'npm' and 'npm-update' make targets and lockfile

- `make npm` installs and updates node_modules, triggered automatically
   on `make css` and `make js` as it completes reasonably fast and
   ensures consistent modules.
- `make npm-update` updates all dependencies to their latest version,
   regenerates `node_modules` from scratch and updates
   `package-lock.json`. It uses npm modules `updates` written by yours
   truly to find the latest version of each dependency.

* add suggested make dependencies

* remove package-lock.json during npm-update

* regenerate package-lock.json

6 years ago

silverwind

04f996f1f9

remove and disable package-lock (#6969 )

* remove and disable package-lock

Using exact versions in package.json has the same effect as lockfiles
without all the troubles the lockfiles bring (different versions of
package manager generating different lockfiles primarily).

Ensured we only use exact versions in package.json and stopped
generation of new lockfiles via .npmrc which is support by both the npm
and yarn package managers.

Fixes: https://github.com/go-gitea/gitea/issues/6967

* enable save-exact

6 years ago

3 Commits (7c8e116987895bf9c67dc133f8aa04a799170a2e)