Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Set
Set
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Ind.ie Projects
  • SetSet
  • Issues
  • #7

Closed
Open
Opened Aug 21, 2017 by Aral Balkan@aralMaintainer
  • Report abuse
  • New issue
Report abuse New issue

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?

Main concerns:

  1. Do not make the current process of working with indie-set any harder (no extra steps)
  2. Try to reduce redundancy (I know these two steps are not necessarily compatible)
  3. When in doubt, go with 1 :)

As per:

@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?

(https://mastodon.social/users/ekaitz_zarraga/updates/4156373)

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?

(https://mastodon.ar.al/@aral/442559)

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?

(https://mastodon.social/users/ekaitz_zarraga/updates/4156410)

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? :)

(https://mastodon.ar.al/@aral/442588)

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 :)

(https://mastodon.social/users/ekaitz_zarraga/updates/4156453)

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: project/set#7

Like this? Fund us! Your patronage helps keep us independent and going.