This website works better with JavaScript.
code
.tokarch.uk
Explore
Help
Sign In
third_party
/
gitea
Watch
1
Star
0
Fork
You've already forked gitea
0
Code
Issues
Pull Requests
Packages
Projects
Releases
Wiki
Activity
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
9467
Commits
2
Branches
0
Tags
240 MiB
Tag:
Branch:
Tree:
ba40263fdd
tokarchuk/v1.17
tokarchuk/v1.18
Branches
Tags
${ item.name }
Create tag
${ searchTerm }
Create branch
${ searchTerm }
from 'ba40263fdd'
${ noResults }
gitea
/
.npmrc
3 lines
34 B
Raw
Normal View
History
Unescape
Escape
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
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
6 years ago
save-exact=true