npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

parcel-reporter-entries

v2.10.3-rc.2

Published

This plugin allows to link entry assets and bundle files.

Downloads

53

Readme

This plugin allows to link entry assets and bundle files.

Why?

It's side effect of another useful plugin - https://github.com/ol-loginov/parcel-namer-rewrite (it able to change bundle names).

After renaming (hashing) you may want to get changed file names.

Configuration

Plugin takes all config from package.json file. Example of config is below:

{
    "name": "...",
    "version": "...",
    "description": "",

  
    "parcel-reporter-entries": {
        "file": "src/main/resources/application-bundle.yml",
        "assetRoot": "src/webapp/scripts" /* path to relativize input assets against */,
        "yml-write": "array",
        "yml-parent": "app/some/parent",
        "yml-array-from": "from",
        "yml-array-to": "to",
    }
}

This example:

  1. write report to 'src/main/resources/application-bundle.yml'.
  2. it creates YAML with array of file names and put it under "app" element of YAML.
    1. "yml-write": "array" | "map". When "array" - files are written like objects in array. When "map" - files are written like key-value of some object
    2. "yml-parent": slash-separated path to element where to put file names map
    3. "yml-array-from": for "array" mode - field for asset file name
    4. "yml-array-to": for "array" mode - field for bundle file name
  3. It uses assetRoot to make relative input asset name. If input assets is 'src/webapp/source/test/script1.js' and assetRootis "src/webapp", then only "source/test/script1.js" will be print as input asset file path

Options for output