Stop publishing all-in-one builds

[cburgmer]

Hey @barillax, in 2571b79 i've made a change to stop publishing the all-in-one packages. I just realised, that we only recently added the non-cssom one.

The benefits of not publishing those is removing the need to provide updates here if some downstream dependency changes. Naturally the user should just get those by running a local npm install.

Can you let me know if that works with your build process / otherwise whether we can come up with a good argument why we should bring back support for these?

[barillax]

Hey @cburgmer , thanks for checking!

So, I recall our original need for inlineresources.allinone.nocssom.js was that our build process didn't use browserify, and the existing allinone (which I presume the version located at https://wzrd.in/standalone/inlineresources@latest would be equivalent to) bundles in CSSOM, which breaks on minified stylesheets. If it weren't for that issue, the wzrd build would be sufficient!

The current version is working great for us, so in the worst case we could simply fork or pin to the current version. I don't want to make a lot of work for you if we're your only non-browserify/webpack user.

[cburgmer]

That's fine, I'm just trying to strike a balance.

I'll sit down and think about what to do. Basically I want:

1. No deps checked in, not even in a all-in-one distributable
2. The library should be easy to include via UMD headers (for AMD, CommonJS and script inclusion), and should make it trivial to get its own dependencies included via old school <script> inclusions.
3. Supports having deps optional.

This generally doesn't seem to be solved in the JS community. I've been reading around a lot, trying different things, but they all seem to cater to slightly different problems. In the end I might just build my own UMD header template on top.

I assume that work for you? In this case you would have to switch to getting hold of url and css-font-face-src as a dependency, which wzrd.in can also offer.

[barillax]

Since our pipeline is to effectively the same as the old school script include approach (namely: concat, uglify, and minify), I think that would work for us. Thanks!

I agree that things are a bit of a mess right now wrt to modules :-(

[cburgmer]

• Provide a way through npm to get hold of the url package with UMD header
• Provide a UMD header version css-font-face-src dependency
• Document dependencies in README