Greetings!
In some docs I’ve seen, I’ve been instructed to run expo install [ package name]
. Curiously, I’ve had a look through the code of the expo cli, but I’m still scratching my head on what the difference is between yarn install
and expo install
. Could anyone shed some light?
We may need some more docs in this area.
/* @flow */
import * as ConfigUtils from '@expo/config';
import fs from 'fs';
import { inflect } from 'inflection';
import JsonFile from '@expo/json-file';
import npmPackageArg from 'npm-package-arg';
import path from 'path';
import { Versions } from '@expo/xdl';
import CommandError from '../CommandError';
import * as PackageManager from '../PackageManager';
import log from '../log';
async function installAsync(packages, options) {
const { projectRoot, workflow } = await findProjectRootAsync(process.cwd());
const packageManager = PackageManager.createForProject(projectRoot, {
npm: options.npm,
yarn: options.yarn,
});
This file has been truncated. show original
Cheers,
Nathan
Hey @nathansimpson ,
expo install
ensures that the package you download is the appropriate one that is compatible with the SDK version your project is running.
Cheers,
Adam
3 Likes
Ah yes, that makes sense. Thank you very much
2 Likes
system
Closed
August 29, 2019, 3:41am
5
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.