npm

Need private packages and team management tools?Check out npm Orgs. »

now-loader

0.0.2 • Public • Published

Webpack Now Loader

Webpack loaders are super cool. You can extract away a require statement at compile time, and do what you want with the file. I thought deploying the required file statically to Now, and using the deployed url at runtime could lead to some cool developer benefits.

For example, in your React file:

const picture = require('now-loader!picture.png');
const resume = require('now-loader!resume.pdf');
 
...
 
<div>
  <img src={picture} alt="A picture of me"/>
  <a href={resume}>Get my resume</a>
</div>

This way, when you run webpack, the loader deploys the picture and the resume, retrieves a now.sh deployment url, and then your codebase hotlinks to them. There seems to be an unnescessary level of indirection here, but consider these:

  • Your static resources are now hosted individually and have shareable links to them. For instance, I use this on my website(pranay.gp) so that my Resume is hosted and accessible from its own deployment (resume.pranay.gp)
  • You can update static dependencies without having to update your website. Using the alias webpack option, the loader can automatically alias your deployment right after creating it, and return the aliased URL instead. That way, in the future, if you build your site again with an updated static resource, it will deploy and alias it correctly, and you don't have to actually re-deploy your website

But that's not all. Here's what I personally think is the coolest thing you can do with it (Works, but still in super super alpha)

const APIendpoint = require('now-loader!../test-backend/package.json');
 
fetch(APIendpoint + '/foo').then(console.log)

On your client codebase, you can simply "require" your entire backend codebase (by either requiring the root package.json, now.json or Dockerfile in your backend codebase). When you run webpack, it'll deploy the latest version of your backend to now, and return the URL to that so you can just use it throughout your client codebase without having to configure (or worse, hardocde the url on) your frontend.

Install

yarn add --dev now-loader
# npm install --save-dev now-loader 

You likely want to use now-loader inline, and not in your webpack.config, but you can use the following rule in your config for full deployments :D

   {
     test: /(now.json|package.json|Dockerfile)/,
     loader: 'now-loader'
   }

Keywords

none

install

npm i now-loader

Downloadsweekly downloads

0

version

0.0.2

license

MIT

last publish

collaborators

  • avatar
Report a vulnerability