Would you consider using npm for client-side dependencies too and browserify or webpack so that you can just require('react') or similar in the front-end code? Most people building modern webapps these days use a similar system and it would be really great if there was a way to get started with this inside the browser, without installing anything – since this is where simpler environments like jsfiddle and codepen start to fall short.
(If that worked seamlessly there’s a good chance we’d want to suggest HyperWeb from the React site in our quick-start section. :))
I had a similar question, though I was looking for a more “lightweight” way of adding client-side dependencies: something like a quick-pick control for CDN-based client depencies, like the ones you find in JS playgrounds and Stack Snippets.
This is especially important if it would be strongly advised to use integrety on script tasks, because it can become tedious to manually construct those script tasks when you’re just prototyping something with HyperWeb.
As a temporary workaround, I suggest using the requirejs library . I understand it is not exactly the same solution, but it at least makes you able to keep dependencies separate and guarantees that the global domain doesn’t get polluted.
Our team will definitely be digging into this, but in the shorter-term we’ve created an alternative solution, which provides well for your use-case I think. So we’ve made it possible for you to remix (copy) a project from a URL. So for example, I’ve created a version of the React tutorial example, and if you provided users with the remix URL then when they click on it, they get their own version of that project that they can play around with in HyperDev - no setup required. Let me know if you think this will work for you, and I can help you to get the remix URL for any projects you want to use as it’s not currently exposed in the UI.
I made this https://hyperdev.com/#!/project/jewel-back using webpack and a postinstall script. It worked for a while, then the bundle.js disappeared (now I copied it manually in a ‘fixed’ file, but this seems like cheating to me…). If you just let the file created by webpack persist on the server we will be able to use the webpack workflow in this way.
It’ll work for the files it needs to create, which didn’t before. However, that would still need console access, which is something we’re still discussing how best to expose. For now, if you’re using it as a boilerplate generator, then an import of a generated project and remix is currently the best way to do that.