@gatsbyjs/parcel-namer-relative-to-cwd

v2.14.0

Parcel namer that preserves directory structures to stabilize output and keep the hierarchy. For more information about how to use this package see README

Latest version published 2 days ago

License: MIT

NPM

GitHub

Package Health Score

95 / 100

security
No known security issues
popularity
Influential project
maintenance
Healthy
community
Active

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
2.14.0	\|	11/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.13.1	\|	01/2024	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.10.0	\|	12/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.0.2	\|	03/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Yes

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

Influential project

Weekly Downloads (140,896)

GitHub Stars: 55.26K
Forks: 10.32K
Contributors: 420

Direct Usage Popularity

The npm package @gatsbyjs/parcel-namer-relative-to-cwd receives a total of 140,896 downloads a week. As such, we scored @gatsbyjs/parcel-namer-relative-to-cwd popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package @gatsbyjs/parcel-namer-relative-to-cwd, we found that it has been starred 55,258 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: 420
Funding: No

A good and healthy external contribution signal for @gatsbyjs/parcel-namer-relative-to-cwd project, which invites more than one hundred open source maintainers to collaborate on the repository.

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 189
Open PR: 204
Last Release: 2 days ago
Last Commit: 1 month ago

Further analysis of the maintenance status of @gatsbyjs/parcel-namer-relative-to-cwd based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @gatsbyjs/parcel-namer-relative-to-cwd demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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: >=18.0.0

Age: 3 years
Dependencies: 4 Direct
Versions: 103
Install Size: 16 kB
Dist-tags: 12
# of Files: 5
Maintainers: 8
TS Typings: No

@gatsbyjs/parcel-namer-relative-to-cwd 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

`@gatsbyjs/parcel-namer-relative-to-cwd`

This namer plugin is used by Gatsby internally. You can reuse it inside your app if you want.

If you're just using Gatsby, you don't need to care about this package/plugin.

Usage

npm install --save-dev @gatsbyjs/parcel-namer-relative-to-cwd

And inside your .parcelrc:

{
  "extends": "@parcel/config-default",
  "namers": ["@gatsbyjs/parcel-namer-relative-to-cwd", "..."]
}

Why & How

By default, Parcel is trying to find common/shared directories between entries and output paths that are impacted by it. See this issue comment for more information.

With these inputs files:

a.html
sub/b.html

You get:

parcel build a.html => dist/a.html
parcel build sub/b.html => dist/b.html
parcel build a.html sub/b.html => dist/a.html, dist/sub/b.html

You can see that sub/b.html entry might result in either dist/b.html or dist/sub/b.html (depending wether a.html is entry or not). This makes builds not deterministic, which is very problematic where entries are "optional".

This namer plugin stabilizes the output, so inside distDir the hierarchy is the same as entry file in relation to current working directory (CWD):

parcel build a.html => dist/a.html
parcel build sub/b.html => dist/sub/b.html
parcel build a.html sub/b.html => dist/a.html, dist/sub/b.html

@gatsbyjs/parcel-namer-relative-to-cwd dependencies

@babel/runtime @parcel/namer-default @parcel/plugin gatsby-core-utils

@gatsbyjs/parcel-namer-relative-to-cwd development dependencies

@babel/cli @babel/core babel-preset-gatsby-package cross-env

FAQs

What is @gatsbyjs/parcel-namer-relative-to-cwd?

Parcel namer that preserves directory structures to stabilize output and keep the hierarchy. Visit Snyk Advisor to see a full health score report for @gatsbyjs/parcel-namer-relative-to-cwd, including popularity, security, maintenance & community analysis.

Is @gatsbyjs/parcel-namer-relative-to-cwd popular?

The npm package @gatsbyjs/parcel-namer-relative-to-cwd receives a total of 140,896 weekly downloads. As such, @gatsbyjs/parcel-namer-relative-to-cwd popularity was classified as an influential project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @gatsbyjs/parcel-namer-relative-to-cwd well maintained?

We found that @gatsbyjs/parcel-namer-relative-to-cwd demonstrated a healthy version release cadence and project activity. It has a community of 420 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is @gatsbyjs/parcel-namer-relative-to-cwd safe to use?

The npm package @gatsbyjs/parcel-namer-relative-to-cwd 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 7 November-2024, at 16:21 (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