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

nitro-exporter

v1.0.1

Published

An exporting package for nitro. Generate static packages with ease.

Downloads

39

Readme

nitro-exporter

With this package, Nitro can generate static exports of your project by using npm run export.

$ npm run export

The exporter configuration can be found in config.json.

Configuration options

exporter.dest (String)

The distribution folder for your static export. This is where all your static files will go.

  • example: "dist"

exporter.i18n (Array)

Contains a list of language keys. The views will be exported using the specified language keys. You have to specify all languages addiotionally for the dump-views task at generator-nitro. The nitro-exporter will export all dumped views per default. You can filter out specific view exports by either setting i18n or views option.

  • example: ["de"]

exporter.publics (Boolean / Array)

Controls which public files should be exported statically. true will export all files from your public directory.

You can define an array of strings, like ["build/assets/css/app.css", "build/assets/js/app.js"] to export only those files.

When defining strings you can use globbing patterns.

  • example: true

exporter.renames (Array)

Defines file renames. Takes an array of objects with src, base and dest. Renaming is used with native gulp.src(...).pipe(gulp.dest(...)).

  • example:

      [{
          "src": "dist/assets/**",
          "base": "dist/assets",
          "dest": "dist/"
      }]

exporter.replacements (Array)

Defines string replacements. Takes an array of objects with glob and replace. replace is an array of objects with keys from and to.

Please note: renames are executed before replacements!

  • example:

      [{
          "glob": ["dist/*.html", "dist/css/*.css"],
          "replace": [{
              "from": "/assets",
              "to": ""
          }]
      }]

exporter.views (Boolean / Array)

Controls which views should be exported statically. true will export all views from your views directory.

You can define an array of strings, like ["index.hbs", "404.hbs"] to export only those views.

When defining strings you can use globbing patterns.

  • example: true

exporter.zip

Defines, if the export should be zipped.

  • example: false

Example Exporter Config

"exporter": {
    "dest": "dist",
    "i18n": [],
    "publics": true,
    "renames": [
        {
            "src": "dist/assets/**",
            "base": "dist/assets",
            "dest": "dist/"
        }
    ],
    "replacements": [
        {
            "glob": ["dist/*.html", "dist/css/*.css"],
            "replace": [
                {
                    "from": "/assets/",
                    "to": ""
                }
            ]
        },
        {
            "glob": ["dist/js/*.js"],
            "replace": [
                {
                    "from": "/api",
                    "to": "api"
                }
            ]
        },
        {
            "glob": ["dist/*.html"],
            "replace": [
                {
                    "from": "([a-z]+)\\.(css|js)",
                    "to": "$1.min.$2"
                }
            ]
        }
    ],
    "views": true,
    "zip": false
}

Multiple Exporter configurations

You can define multiple exporter configuration objects, by setting the exporter to an array.

Example

"exporter": [{
    "dest": "dist",
    "i18n": [],
    "publics": true,
    "renames": [],
    "replacements": [],
    "views": true,
    "zip": false
}, {
    "dest": "static",
    "i18n": [],
    "publics": true,
    "renames": [],
    "replacements": [],
    "views": true,
    "zip": false
}]