check-export-map

v1.3.1

Check if entries in an export map in package.json are valid and point to actual files/folders For more information about how to use this package see README

Latest version published 1 year ago

License: MIT

NPM

GitHub

Package Health Score

49 / 100

security
No known security issues
popularity
Limited
maintenance
Inactive
community
Limited

Security

No known security issues

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
1.3.1	\|	11/2023	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.2.0	\|	11/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.1.1	\|	05/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.0.1	\|	09/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

Limited

Weekly Downloads (910)

GitHub Stars: 56
Forks: 6
Contributors: 4

Direct Usage Popularity

The npm package check-export-map receives a total of 910 downloads a week. As such, we scored check-export-map popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package check-export-map, we found that it has been starred 56 times.

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

Community

Limited

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

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like check-export-map is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 3
Open PR: 1
Last Release: 1 year ago
Last Commit: 1 year ago

Further analysis of the maintenance status of check-export-map 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 check-export-map 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: 4 years
Dependencies: 2 Direct
Versions: 8
Install Size: 18.2 kB
Dist-tags: 1
# of Files: 61
Maintainers: 1
TS Typings: No

check-export-map 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.

Readme

Check export maps

A simple cli tool that checks if the export map defined in a package.json file is correct and that the referenced files/folders exist.

Rules:

Entries must start with a .
Must have the following entries:
- . = main export when you do import * as foo from "my-package"
- ./package.json = allow user to import the package's package.json file
Entry type import must end with .mjs
Entry file paths must be relative and start with a .
All referenced files/folders must exist on disk

Example of a valid export map in package.json:

{
  "name": "preact",
  "exports": {
    ".": {
      "browser": "./dist/preact.module.js",
      "umd": "./dist/preact.umd.js",
      "import": "./dist/preact.mjs",
      "require": "./dist/preact.js"
    },
    "./compat": {
      "browser": "./compat/dist/compat.module.js",
      "umd": "./compat/dist/compat.umd.js",
      "import": "./compat/dist/compat.mjs",
      "require": "./compat/dist/compat.js"
    },
    "./compat/server": {
      "require": "./compat/server.js"
    },
    "./package.json": "./package.json"
  }
}

Usage

Add the package via:

npm install -D check-export-map
# yarn
yarn add -D check-export-map

...and add an script to your package.json:

{
	"name": "my-package",
	"scripts": {
		"test": "check-export-map"
	}
}

Global installation

You can install check-export-map globally to invoke it from any directory.

npm install -g check-export-map

CLI documentation

Check if the export map declared in package.json is valid.

Usage
  check-export-map [options] &lt;...FILES&gt;
	
Options
  -v, --version    Displays current version
  -h, --help       Displays this message

LICENSE

MIT, see the LICENSE file.

check-export-map dependencies

kolorist mri

check-export-map development dependencies

@changesets/changelog-github @changesets/cli @types/mocha @types/node husky lint-staged mocha prettier

FAQs

What is check-export-map?

Check if entries in an export map in package.json are valid and point to actual files/folders. Visit Snyk Advisor to see a full health score report for check-export-map, including popularity, security, maintenance & community analysis.

Is check-export-map popular?

The npm package check-export-map receives a total of 910 weekly downloads. As such, check-export-map popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is check-export-map well maintained?

We found indications that check-export-map is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is check-export-map safe to use?

The npm package check-export-map was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 15 December-2024, at 21:45 (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