forgejo

mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-12-23 07:43:18 -05:00

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> 2020-01-12 18:11:43 -05:00			`package-lock=true`
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 2019-05-16 14:33:54 -05:00			`save-exact=true`