mtscout6/knockout — comment on commit 327f87b0a2d634ff3c473db1e6c249a098f80b92
File:  line 0
By SteveSanderson:

Thanks for this!

I'm definitely happy to take the changes that pass `document` and `navigator` into the scope wrapper.

The NPM-specific build, however, might be better kept in a separate repo. The central KO repo doesn't currently include builds for all the many different package formats that people are using (Gem, NuGet, NPM, ...), and if it did include build scripts for all of them, it would be very unweildy - not only would there be tons of extra files, but the build would become either more manual (having to run multiple build scripts instead of just one) or more complex (automating the execution of builds for all the different package formats).

Currently I'm maintaining a Knockout NuGet package in a separate repo at https://github.com/SteveSanderson/knockout.nuget - it takes very little work to update and publish that each time there's a new official KO release. Along those lines, do you think it would make sense to have a separate knockout.npm repo for the NPM-specific bits? The code you've written (with the `package.json` and the `node-npm-header.js`) could easily be the basis for that, and it could import the latest KO bits either by using a Git submodule, or just by scripting a `wget` or `curl` to pull in prebuilt files from https://github.com/SteveSanderson/knockout/tree/master/build/output.

Thoughts?