Do you plan to release this on npm?

[rememberlenny]

No description provided.

[rememberlenny]

More background here. I'm currently using samsa-core installed through package.json and imported in the files accessing the SamsaFont method. Its possible to call the library from a direct github reference, but an npm release would be useful for others.

[Lorp]

Someone else asked about this a while ago. It’ll happen.

[kontur]

🤞

[Lorp]

Hi @kontur, @rememberlenny: can you advise the best way to make this happen?

[kontur]

Hey @Lorp I've only published one package myself, but it's rather straight forward. You need an npm account and the publishing and updating happens straight from the console via npm commands. You already have a package.json, so it's just getting it registered to npm. This should be an exhaustive guide.

That would make installing code to other projects more easy, and doesn't enforce any kind of module or other structure to the package per se. The other day I've tried to use Samsa standalone to parse and extract some SVGs, with moderate success. The standalone sample with the linked files works, but I couldn't get it to work when importing e.g. to a browserify/babel compile pipeline. I'll try that some more next week and report back (in a separate issue) if that yields some other suggestions on how to make your excellent code more reusable — also quite likely I just don't know how to properly set it up :D I do think though that samsa-core has some globals floating around that are then missing when importing the module to projects.