npm is just a repository.
A repository exists in Python, Ruby, ArchLinux (AUR), Debian, etcetera.
A repository purpose is to publish a program/module/library that can be
reused across projects.
A repository doesn't force you to create dependencies.
A repository doesn't need your code to be com
One of the issues I have with NPM support, is that then brings the
undesirable hundreds of package dependencies through encouraging the
use of them.
If someone *does* use NPM packages and creates an app with this
support, then that introduces some seriously big headaches with
packaging for distros.
If until now GJS ignored the rest of the world in terms of JS modules and
the ability to use npm as registry, I believe I'm not the one that can
answer that question but I am 100% sure if you want GJS to be more popular,
you need a better JS ecosystem integration, and npm is mandatory step zero
to
The cgjs/utilities experiment became a quite useful stand alone utility to
introspect at runtime GJS classes and gi avaliable namespaes.
More details here:
https://github.com/WebReflection/cgjs-about
You can install it via `npm install -g cgjs-about` and then try one of
these commands:
cgjs-abou
On Fri, Nov 3, 2017 at 3:16 PM Andrea Giammarchi <
andrea.giammar...@gmail.com> wrote:
> yeah, that's why I need help/contributors there.
>
> The fs is relatively trivial, streams are more painful but in JSGtk the fs
> was already working.
>
> I am just starting porting over and improving JSGtk, t
