@expo/dev-tools

v0.13.187

The Expo Dev Tools UI has been deprecated. [Learn more](https://blog.expo.dev/sunsetting-the-web-ui-for-expo-cli-ab12936d2206). For more information about how to use this package see README

Latest version published 1 year ago

License: MIT

NPM

GitHub

Package Health Score

56 / 100

security
Security review needed
popularity
Recognized
maintenance
Inactive
community
Active

Explore Similar Packages

react-native
89

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version			Vulnerabilities	License Risk
0.13.187	\|	08/2023	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.13.126	\|	10/2021	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.12.6	\|	04/2020	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.11.0	\|	04/2020	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.10.35	\|	04/2020	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Recognized

Weekly Downloads (1,810)

GitHub Stars: 2.61K
Forks: 478
Contributors: 180

Direct Usage Popularity

The npm package @expo/dev-tools receives a total of 1,810 downloads a week. As such, we scored @expo/dev-tools popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package @expo/dev-tools, we found that it has been starred 2,613 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 180
Funding: No

A good and healthy external contribution signal for @expo/dev-tools project, which invites more than one hundred open source maintainers to collaborate on the repository.

Embed Package Health Score Badge

Maintenance

Inactive

archived

Commit Frequency

Open Issues: 0
Open PR: 0
Last Release: 1 year ago
Last Commit: 11 months ago

Further analysis of the maintenance status of @expo/dev-tools based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for @expo/dev-tools is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 7 years
Dependencies: 10 Direct
Versions: 425
Install Size: 1.51 MB
Dist-tags: 4
# of Files: 71
Maintainers: 28
TS Typings: No

@expo/dev-tools has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use @expo/dev-tools?

To help you get started, we've collected the most common ways that @expo/dev-tools is being used within popular public projects.

expo / expo-cli / packages / expo-cli / src / commands / start.js View on Github

async function action(projectDir, options) {
  installExitHooks(projectDir);

  await urlOpts.optsAsync(projectDir, options);

  log(chalk.gray('Starting project at', projectDir));

  let rootPath = path.resolve(projectDir);
  let devToolsUrl = await DevToolsServer.startAsync(rootPath);
  log(`Expo DevTools is running at ${chalk.underline(devToolsUrl)}`);

  const { exp } = await ProjectUtils.readConfigJsonAsync(projectDir);
  if (exp === null) {
    log.warn('No Expo configuration found. Are you sure this is a project directory?');
    process.exit(1);
  }

  const nonInteractive = options.parent && options.parent.nonInteractive;
  if (!nonInteractive && !exp.isDetached) {
    if (await UserSettings.getAsync('openDevToolsAtStartup', true)) {
      log(`Opening DevTools in the browser... (press ${chalk.bold`shift-d`} to disable)`);
      opn(devToolsUrl, { wait: false });
    } else {
      log(
        `Press ${chalk.bold`d`} to open DevTools now, or ${chalk.bold`shift-d`} to always open it automatically.`

View more ways to use @expo/dev-tools

@expo/dev-tools dependencies

lodash express graphql iterall base64url better-opn @expo/config graphql-tools freeport-async subscriptions-transport-ws

FAQs

What is @expo/dev-tools?

The Expo Dev Tools UI has been deprecated. [Learn more](https://blog.expo.dev/sunsetting-the-web-ui-for-expo-cli-ab1293... Visit Snyk Advisor to see a full health score report for @expo/dev-tools, including popularity, security, maintenance & community analysis.

Is @expo/dev-tools popular?

The npm package @expo/dev-tools receives a total of 1,810 weekly downloads. As such, @expo/dev-tools popularity was classified as a recognized. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @expo/dev-tools well maintained?

We found indications that @expo/dev-tools is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is @expo/dev-tools safe to use?

While scanning the latest version of @expo/dev-tools, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 13 November-2024, at 08:35 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

@expo/dev-tools

The Expo Dev Tools UI has been deprecated. [Learn more](https://blog.expo.dev/sunsetting-the-web-ui-for-expo-cli-ab12936d2206). For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (1,810)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Not sure how to use @expo/dev-tools?

@expo/dev-tools

@expo/dev-tools dependencies

@expo/dev-tools development dependencies

FAQs

What is @expo/dev-tools?

Is @expo/dev-tools popular?

Is @expo/dev-tools well maintained?

Is @expo/dev-tools safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (1,810)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use @expo/dev-tools?

@expo/dev-tools

@expo/dev-tools dependencies

@expo/dev-tools development dependencies

FAQs

What is @expo/dev-tools?

Is @expo/dev-tools popular?

Is @expo/dev-tools well maintained?

Is @expo/dev-tools safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues