THIS IS A TEST INSTANCE ONLY! REPOSITORIES CAN BE DELETED AT ANY TIME!
Logo
Explore Help
Sign In
lianguan/gitea
1
0
Fork 0
You've already forked gitea
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity
Files
4e10f33349e30c08b6e55c6dea20ec1fb6c39d9a
gitea/.npmrc

3 lines
34 B
Plaintext
Raw Normal View History

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-13 00:11:43 +01: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 21:33:54 +02:00
save-exact=true
Reference in New Issue Copy Permalink
Powered by Gitea Version: 1.26.0+dev-392-g94437eadd9 Page: 14317ms Template: 1345ms
Auto
English
Bahasa Indonesia Deutsch English Español Français Gaeilge Italiano Latviešu Magyar nyelv Nederlands Polski Português de Portugal Português do Brasil Suomi Svenska Türkçe Čeština Ελληνικά Български Русский Українська فارسی മലയാളം 日本語 简体中文 繁體中文(台灣) 繁體中文(香港) 한국어
Licenses API