| /expo/packages/@expo/package-manager/src/node/__tests__/ |
| H A D | NpmPackageManager-test.ts | 21 expect(npm.name).toBe('npm');
27 await npm.installAsync();
40 await npm.installAsync();
142 await npm.installAsync();
176 await npm.uninstallAsync();
185 await npm.uninstallAsync();
199 await npm.addAsync();
218 await npm.addAsync(['expo']);
305 await npm.addDevAsync();
411 await npm.addGlobalAsync();
[all …]
|
| /expo/docs/pages/troubleshooting/ |
| H A D | clear-cache-macos-linux.mdx | 24 ### Expo CLI and npm
28 npm cache clean --force
29 npm install
49 ### React Native CLI and npm
53 npm cache clean --force
54 npm install
58 npm start -- --reset-cache
63 … internet before you run them. We explain each command below for Expo CLI, npm, and Yarn, but the …
69 | `npm cache clean --force` | Clear the global npm cache …
70 | `yarn`/`npm install` | Reinstall all dependencies …
|
| H A D | clear-cache-windows.mdx | 22 ### Expo CLI and npm
26 npm cache clean --force
27 npm install
47 ### React Native CLI and npm
51 npm cache clean --force
52 npm install
56 npm start -- --reset-cache
61 … internet before you run them. We explain each command below for Expo CLI, npm, and Yarn, but the …
67 | `npm cache clean --force` | Clear the global npm cache …
68 | `yarn`/`npm install` | Reinstall all dependencies …
|
| /expo/docs/pages/build-reference/ |
| H A D | infrastructure.mdx | 77 - npm 8.19.2
91 - npm 8.19.2
105 - npm 8.19.2
119 - npm 8.19.2
133 - npm 8.19.2
147 - npm 8.19.2
194 - npm 8.1.2
210 - npm 8.1.2
226 - npm 8.19.2
242 - npm 8.19.2
[all …]
|
| H A D | private-npm-packages.mdx | 2 title: Use private npm packages
3 description: Learn how to configure EAS Build to use private npm packages.
8 …S Build has full support for using private npm packages in your project. These can either be publi…
10 …arting the build, you will need to configure your project to provide EAS Build with your npm token.
12 ## Default npm configuration
14 By default, EAS Build uses a self-hosted npm cache that speeds up installing dependencies for all b…
19 registry=http://npm-cache-service.worker-infra-production.svc.cluster.local:4873
28 ## Private packages published to npm
30 … project is using private packages published to npm, you need to provide EAS Build with [a read-on…
59 If you're using a private npm registry such as self-hosted [Verdaccio](https://verdaccio.org/), you…
[all …]
|
| H A D | npm-cache-with-yarn.mdx | 2 title: Use npm cache with Yarn Classic
4 description: Learn how to use npm cache by overriding the registry in Yarn Classic.
7 By default, the EAS npm cache won't work with Yarn 1 (Classic), because **yarn.lock** files contain…
9 If you want to take advantage of the npm cache, you can add the `eas-build-pre-install` npm hook in…
|
| H A D | npm-hooks.mdx | 3 description: Learn how to use the EAS Build lifecycle hooks with npm to customize your build proces…
6 There are five EAS Build lifecycle npm hooks that you can set in your **package.json**. See the [An…
8 - `eas-build-pre-install` - executed before EAS Build runs `npm install`.
10 …- Android - runs once after the following commands have all completed: `npm install` and `npx expo…
11 …- iOS - runs once after the following commands have all completed: `npm install`, `npx expo prebui…
|
| /expo/packages/@expo/cli/src/install/__tests__/ |
| H A D | resolveOptions-test.ts | 9 /Specify at most one of: --npm, --pnpm, --yarn/
12 /Specify at most one of: --npm, --pnpm, --yarn/
30 npm: false,
45 npm: true,
|
| /expo/docs/pages/modules/ |
| H A D | use-standalone-expo-module-in-your-project.mdx | 12 - [Publish the module to npm](#publish-the-module-to-npm)
49 cmdCopy="cd packages/expo-settings && npm run build"
50 cmd={['$ cd packages/expo-settings', '$ npm run build']}
89 ## Publish the module to npm
106 '$ npm run build',
123 ### 3. Publish the package to npm
125 To publish your package to npm, you need to have an npm account. If you don't have one, create it o…
127 <Terminal cmd={['$ npm login']} />
131 <Terminal cmd={['$ npm publish']} />
133 Your module will now be published to npm and can be installed in other projects using `npm install`.
[all …]
|
| /expo/packages/expo-module-scripts/ |
| H A D | CONTRIBUTING.md | 1 ## Test with both Yarn and npm
3 …the Expo repo, we use npm to publish packages. For scripts that run when publishing, make sure to …
5 … root and package's .bin directories to `PATH`. We need to do the same for npm so that it finds in…
|
| H A D | README.md | 14 - [�� npm Linking](#-npm-linking)
23 - [prepare (npm lifecycle)](#prepare--npm-lifecycle-)
24 - [prepublishOnly (npm lifecycle)](#prepublishonly--npm-lifecycle-)
25 - [Excluding Files from npm](#excluding-files-from-npm)
35 npm install --save-dev expo-module-scripts
200 ### �� npm Linking
202 Make your package accessible to npm users by adding the following fields:
235 For scripts that need to run as part of the npm lifecycle, you'd invoke the commands from npm scrip…
301 ### prepare (npm lifecycle)
305 ### prepublishOnly (npm lifecycle)
[all …]
|
| /expo/ios/versioned-react-native/ABI47_0_0/ReactNative/scripts/circleci/ |
| H A D | analyze_code.sh | 12 cat <(echo eslint; npm run lint --silent -- --format=json; echo flow; npm run flow-check-ios --sile…
|
| /expo/ios/versioned-react-native/ABI48_0_0/ReactNative/scripts/circleci/ |
| H A D | analyze_code.sh | 12 cat <(echo eslint; npm run lint --silent -- --format=json; echo flow; npm run flow-check-ios --sile…
|
| /expo/docs/pages/build/ |
| H A D | building-on-ci.mdx | 74 - ~/.npm
76 - npm install -g npm@latest
83 - npm ci
99 - .npm
107 - npm ci --cache .npm
129 npm: ~/.npm
137 - npm
140 - npm ci
166 command: npm ci
202 cache: npm
[all …]
|
| /expo/scripts/ |
| H A D | download-dependencies.sh | 11 require npm
14 require yarn || npm install -g yarn
|
| /expo/packages/@expo/cli/src/prebuild/ |
| H A D | prebuildAsync.ts | 53 npm?: boolean;
100 if (hasNewDependencies && options.packageManager?.npm) {
105 npm: !!options.packageManager?.npm,
|
| H A D | resolveOptions.ts | 13 npm: args['--npm'],
20 [managers.npm, managers.pnpm, managers.yarn, managers.bun, !!args['--no-install']].filter(
|
| /expo/packages/@expo/cli/src/install/ |
| H A D | resolveOptions.ts | 19 if ([options.npm, options.pnpm, options.yarn, options.bun].filter(Boolean).length > 1) {
45 npm: !!flags['--npm'],
|
| /expo/packages/@expo/package-manager/src/utils/ |
| H A D | nodeManagers.ts | 39 npm: findYarnOrNpmWorkspaceRoot,
70 npm: NPM_LOCK_FILE,
102 if (options.npm) {
|
| /expo/packages/create-expo-module/build/ |
| H A D | resolvePackageManager.js.map | 1 …npm' | 'pnpm' | 'yarn' | 'bun';\n\n/** Determine which package manager to use for installing depen…
|
| /expo/docs/ui/components/PageTitle/ |
| H A D | PageTitle.test.tsx | 6 test('displays npm registry link', () => {
11 screen.getByTitle('View package in npm Registry');
|
| /expo/packages/@expo/package-manager/build/utils/ |
| H A D | nodeManagers.js | 22 npm: nodeWorkspaces_1.findYarnOrNpmWorkspaceRoot, property
47 npm: nodeWorkspaces_1.NPM_LOCK_FILE, property
72 if (options.npm) {
|
| /expo/apps/jest-expo-mock-generator/ |
| H A D | .gitignore | 3 /npm-debug.*
|
| /expo/packages/expo-module-scripts/templates/ |
| H A D | README.md | 20 ### Add the package to your npm dependencies
23 npm install ${packageName}
29 Run `npx pod-install` after installing the npm package.
|
| /expo/packages/create-expo/template/ |
| H A D | gitignore | 4 npm-debug.*
|