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

cartero-builtin-express-middleware

v0.1.0

Published

Cartero middleware for express that starts cartero for each view.

Downloads

3

Readme

cartero-builtin-express-middleware

See cartero-express-middleware

This is a cartero middleware that actually creates a cartero instance and starts the process for each of your views (parcels).

This means that you dont need to manually start cartero, and it means as well that only the pages you are working at that moment will have a processing delay.

This was done to improve build performance in the development phase. In theory, it can be used in production, if you trust the code, you could update parcels/code and it would automatically refresh your code if you activated the watch option in cartero.

Options

  • cache
    • boolean that indicates if you want to store your parcels cached
    • Should match carteroOptions.watch option.
  • outputDirUrl
    • this is the context path url required to access the output dir. If your cartero results are in ./public/assets, this should then be /assets (if your public is matched to / in your app).
  • outputDirPath
    • the actual path to the output directory
  • carteroOptions
    • options to be given to cartero, based on cartero api. See cartero
    • be aware, if you use packageTransform, instead of passing a Function, you must pass a path to be required

Install

npm install cartero-builtin-express-middleware --save

Example

...
app = express()
...
pkg = require '../../package.json'
app.use require('cartero-builtin-express-middleware')
  cache: app.settings.env isnt "development"
  outputDirUrl : assetsContextPath
  outputDirPath: assetsDir
  carteroOptions:
    watch: true
    appTransforms: [
      "browserify-plain-jade",
      "coffeeify",
      "browserify-shim",
      "less-css-stream"
    ]
    appTransformDirs:[
      process.cwd(),
      path.resolve(process.cwd(), 'node_modules')
    ]
    sourceMaps: false
    packageTransform: path.resolve __dirname, './myTransform'
...

Changes History

  • 0.0.2
    • Added support for packageTransform
  • 0.0.1
    • First release

Problems

  • If you try to open the same page at the same time, if cartero did not init for that page, it may init multiple times.