NativeScript / NativeScript/nativescript-cli
Unable to use Yarn 2+
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- JavaScript
- Estrellas
- 1.1k
- Forks
- 204
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 8
Descripción
Issue Description
I'm trying to use yarn as my package manager, but ns build android fails with the following error: Command failed: yarn config get registry.
Seems like that config value doesn't exist anymore in Yarn 2+. It may have been renamed to the following:
❯ yarn config get npmRegistryServer
https://registry.yarnpkg.com
This seems to be the place where the command is ran:
https://github.com/NativeScript/nativescript-cli/blob/bb3a6965792cc565ab6d516c30a640ac98313ee7/lib/yarn-package-manager.ts#L127
Reproduction
Steps I've taken:
corepack enableyarn set version berryyarn install- Removed
package-lock.json ns package-manager set yarnns cleanns build android
Relevant log output (if applicable)
Build output:
❯ ns build android
(node:28069) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /workspaces/way-app/node_modules/vuex/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
Preparing project...
(node:28118) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /workspaces/way-app/node_modules/vuex/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
assets by path assets/flags/*.png 53.2 KiB
asset assets/flags/bn.png 847 bytes [compared for emit] [from: app/assets/flags/bn.png] [copied]
+ 195 assets
assets by path fonts/ 6.48 MiB 41 assets
assets by path assets/css/ 147 KiB
assets by path assets/css/*.scss 17.1 KiB 7 assets
assets by path assets/css/*.css 130 KiB 2 assets
assets by path *.js 13.5 MiB
asset vendor.js 11.5 MiB [compared for emit] (name: vendor) (id hint: defaultVendor)
asset bundle.js 2.06 MiB [compared for emit] (name: bundle)
asset runtime.js 13.2 KiB [compared for emit] (name: runtime)
assets by path assets/json/*.json 186 KiB
asset assets/json/LottieSpinningCar.json 92.9 KiB [compared for emit] [from: app/assets/json/LottieSpinningCar.json] [copied]
asset assets/json/LottieTest.json 92.9 KiB [compared for emit] [from: app/assets/json/LottieTest.json] [copied]
asset assets/images/NativeScript-Vue.png 8.22 KiB [compared for emit] [from: app/assets/images/NativeScript-Vue.png] [copied]
Entrypoint bundle 13.5 MiB = runtime.js 13.2 KiB vendor.js 11.5 MiB bundle.js 2.06 MiB
runtime modules 2.84 KiB 9 modules
orphan modules 542 bytes [orphan] 7 modules
modules by path ./node_modules/ 4.33 MiB
javascript modules 4.07 MiB 510 modules
json modules 273 KiB
modules by path ./node_modules/mdn-data/css/*.json 242 KiB 3 modules
modules by path ./node_modules/css-tree/ 30.7 KiB 2 modules
modules by path ./app/ 559 KiB 437 modules
external "~/package.json" 42 bytes [optional] [built] [code generated]
webpack 5.71.0 compiled successfully in 7030 ms
Webpack compilation complete.
(node:28069) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /workspaces/way-app/node_modules/@nativescript/core/node_modules/tslib/package.json.
Update this package.json to use a subpath pattern like "./*".
Command failed: yarn config get registry
### Environment
Using Yarn 3.2.0
Using Node 16.14.0
### Please accept these terms
- [X] I have searched the [existing issues](https://github.com/NativeScript/nativescript-cli/issues) as well as [StackOverflow](https://stackoverflow.com/questions/tagged/nativescript) and this has not been posted before
- [X] This is a bug report
- [X] I agree to follow this project's [Code of Conduct](https://github.com/NativeScript/NativeScript/blob/master/tools/notes/CONTRIBUTING.md#coc)
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza en lib/yarn-package-manager.ts con el comando referenciado alrededor de la línea 127 y reproduce el problema con Yarn 3.2.0 usando la configuración de NativeScript indicada y ns build android. Comprueba la búsqueda de configuración de Yarn involucrada y verifica que la compilación de Android se complete sin el fallo de comando informado.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- android, javascript, node.js
- Área
- build-system, cli, mobile-dev
- Tipo de issue
- Error
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Estado de actividad
- Estancado
- Claridad
- Bien especificado
- Aptitud para principiantes
- 45/100