This website works better with JavaScript.
Explore
Help
Register
Sign In
MIROCOD
/
Platform_Mirocod
Watch
13
Star
3
Fork
You've already forked Platform_Mirocod
0
Wiki
Issues
89
resources
competences
Projects
8
Code
Pull Requests
Releases
Activity
Платформа ЦРНП "Мирокод" для разработки проектов
https://git.mirocod.ru
gitea
github
go
golang
mirocod
project-tree
user-map
task-tree
10379
Commits
14
Branches
154
Tags
505 MiB
Tree:
f40a2a4404
Platform_Mirocod
/
.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