Для этого сайта требуется поддержка JavaScript.
Обзор
Помощь
Регистрация
Вход
go-gitea
/
gitea
зеркало из
Следить
1
В избранное
0
Форкнуть
Вы уже форкнули gitea
0
Код
Задачи
Пакеты
Проекты
Релизы
Вики
Активность
c58edc7c78
gitea
/
.npmrc
3 строки
34 B
Plaintext
Исходник
Обычный вид
История
Убрать экранирование
Экранировать
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 02:11:43 +03: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 22:33:54 +03:00
save-exact=true