Enhancement: create “browserfiable” npm package of core Set JS engine
Perhaps the best thing is to create a separate project? (indie-set-engine)
Or is there an easy way to export another NPM package from the same project?
- Do not make the current process of working with indie-set any harder (no extra steps)
- Try to reduce redundancy (I know these two steps are not necessarily compatible)
- When in doubt, go with 1 :)
@aral We can also take a look to Express as a dependency.
I mean, separate the express part in a different package to make Set work directly on the browser with no backend deps, and also let the users get the express part.
This is possible right?
You can already use Set directly in the browser, just include set.js from coffee/lib/set (see the Mastodon client-side updates sample for an example: https://ind.ie/labs/set/posts-client-side-updates)
Perhaps we should make this clearer in the documentation?
Yeah, it's possible but it's not easy.
Do you know browserify? The module like it is right now it's not "browserifiable".
We can do a "indie-set" module with only the set.js file and use it as a dep "indie-set-express". This way if someone makes >something for the browser can also require(indie-set) in a simple way with a cool dependence handler.
While the server-side guys have the whole thing.
Get what I mean?
Can we do it the other way around? Keep indie-set what it is (so as not to break all existing projects) and create, say, an indie-set-browser (or similar) project with just set.js? I’m all for making the project more easily accessible to a larger group of people and this sounds like one way to do it. Sound good? :)
Maybe better than indie-set-browser, indie-set-engine or something like that. :D
But yeah, we totally could!
Open an issue and assign it to me :)