Why are you using Node

[ghost]

This is not JavaScript

[mklement0]

Ah, I see - it's a good thing I didn't go with my initial choice of name, "javascripti". 😜

The truth is that I was already familiar with npm as a capable cross-platform package repository and manager that can also handle CLIs, and I didn't want to spend the time learning how to publish to CPAN too.

Do you think limiting the availability to npm makes many people miss out on / not bother with perli?

[ghost]

its just... weird

technically its fine, but personally i think the whole Node project is ridiculous

javascript isnt and wasnt ever meant to be a systems programming language, it just seems like the whole project is people trying to ram a square into a circle

then you get projects like Electron and shudder

i think youd be much better off on https://metacpan.org

[smac89]

Part of the fun of programming is being able to discover new ways to use existing tools rather than re-inventing the wheel or resorting to manually doing what you need.

NPM is a package manager designed to work for JavaScript projects, but it doesn't mean it only has to work for JavaScript. If you look in the package.json file, it only has a devDependencies section, which should give you a clue as to what NPM is doing here.

Same reason why most GTK python projects use meson as a package manager even though meson does not list python as one of the languages it supports. They use it because meson is a more configurable option than setup.py, for cross-platform development

[ernstki]

Agreed, in principle, and I was also surprised at this, given the relative—relative!—ease with which you're able to get CPAN packages on any system with Perl already installed.

But this made me laugh at my own (negative) assumptions about npm, mostly because I don't really use it as a developer, just an end user.

If I had experience somewhere else, I'm not sure I'd go willingly, either, into the dark pit of briny tentacles that is Perl packaging.

Stay weird, everyone. :)