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

static-file-loader

v0.6.0

Published

file-loader that stores a map of original file names to file names with hashes in the compilation stats

Downloads

136

Readme

static-file-loader

Build Status

Drop-in replacement for file-loader with the only difference: static-file-loader stores a map of original file names to file names with hashes in the compilation stats:

{
  "/Users/koss/src/kossnocorp/static-file-loader/test/fixtures/static/a.gif": "/980d0a50ac153b475e9fb1b8ffe22619.gif",
  "/Users/koss/src/kossnocorp/static-file-loader/test/fixtures/static/b.gif": "/980d0a50ac153b475e9fb1b8ffe22619.gif",
  "/Users/koss/src/kossnocorp/static-file-loader/test/fixtures/static/c.gif": "/980d0a50ac153b475e9fb1b8ffe22619.gif"
}

It's helpful if you want to use webpack to pre-build static files and then build HTML template using the paths map.

Installation

npm install static-file-loader file-loader --save-dev

Example

In an entry:

require.context('!!static-file-loader!./static', true, /.+/)

// ...

Template:

<!DOCTYPE html>
<html>
  <head>
    <meta charset='utf-8' />
    <link rel='shortcut icon' href='<%= staticPath('favicon.png') %>' />
  </head>
  <body>
    <!-- ... -->
  </body>
</html>

Development server:

// ...

var staticFilesPath = path.join(process.cwd(), 'static')
var publicPath = webpackConfig.output.publicPath

express()
  .use('/', express.static(staticFilesPath))
  .get('*', function(req, res) {
    var html = template({
      staticPath: function(staticFilePath) {
        return path.join(publicPath, staticFilePath)
      }
    })
    res.send(html)
  })

Production build script:

// ...

var staticMapKey = require('static-file-loader').key
var staticFilesPath = path.join(process.cwd(), 'assets')
var publicPath = webpackConfig.output.publicPath

webpack(webpackConfig).run(function(err, stats) {
  var staticMap = stats.compilation[staticMapKey]
  var html = template({
    staticPath: function(staticFilePath) {
      var processedStaticFilePath = staticMap[path.join(staticFilesPath, staticFilePath)]
      return path.join(publicPath, processedStaticFilePath)
    }
  })

  // ...
})

License

MIT