petehunt / commonjs-asset-spec Goto Github PK

I was wondering why you encourage an npm package.json instead of bower since the former is geared towards server-side js (although it supports client-side js) where as the latter is explicitly for the front-end.

Can you talk a bit about why you're replacing the url(...) call in CSS with requireStatic(...)? There's prior examples of projects just using url() to require assets: Webpack, Atomify.

The explicitness of "hey, I'm importing this" is nice, but are there any other benefits I'm missing?

Hi, Pete, not an issue, just wondering if you have a vague ETA on this open-sourcing and I never catch you on IRC. 1 month? 3 months? 6? I'm starting a personal project and considering options. Thanks!

Are they needed?

Isn't it closer to the metal to just write your image urls in css url() and html <img> ?

All the places that refer to an image are inside data formats that can be parsed and traversed for outgoing dependencies. Example implementations are available in Assetgraph:

• CSS url(),
• HTML apple-touch-startup-image
• HTML msapplication-TileImage
• HTML <img>
• HTML srcset