Explorar el Código

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
tags/v1.9.0-rc1
silverwind hace 5 años
padre
commit
04f996f1f9
Se han modificado 4 ficheros con 5 adiciones y 3075 borrados
  1. 2
    0
      .gitignore
  2. 2
    0
      .npmrc
  3. 0
    3074
      package-lock.json
  4. 1
    1
      package.json

+ 2
- 0
.gitignore Ver fichero

@@ -67,6 +67,8 @@ coverage.all
/node_modules
/modules/indexer/issues/indexers
routers/repo/authorized_keys
/package-lock.json
/yarn.lock

# Snapcraft
snap/.snapcraft/

+ 2
- 0
.npmrc Ver fichero

@@ -0,0 +1,2 @@
package-lock=false
save-exact=true

+ 0
- 3074
package-lock.json
La diferencia del archivo ha sido suprimido porque es demasiado grande
Ver fichero


+ 1
- 1
package.json Ver fichero

@@ -5,7 +5,7 @@
"eslint": "5.16.0",
"less": "3.9.0",
"less-plugin-clean-css": "1.5.1",
"lesshint": "^6.3.6",
"lesshint": "6.3.6",
"postcss-cli": "6.1.2"
},
"browserslist": [

Cargando…
Cancelar
Guardar