Could you publish a new version to npm?

#1 · open · 3 comments

View on GitHub ↗

suchipi

Hello! Thank you for making this clean, small, zero-dependency package!! :star_struck: I needed something just like this, so I was really happy to find this! It looks like the version on npm has different options/features than what's here on GitHub. Could you please publish a new version?

Comments

Alhadis

👋 Hey @suchipi, It's… _almost_ finished. The documentation is incomplete (primarily concerning syntax colours), and there's a bug with [`gjs`](https://gitlab.gnome.org/GNOME/gjs/-/blob/master/NEWS) where an exception is thrown just from reading the value of a (static) property; i.e., not a getter method (which is weird…) I'll see what I can do about getting this finished. 👍

Alhadis

I see you've made a fork. If you need the unpublished changes in a hurry (say, for a project that depends on it) you can always declare the GitHub repository itself as a dependency: ~~~json "devDependencies": { "print": "Alhadis/Print" } ~~~ Since you've already cut a release, I should inform you that your v2.0.0 won't be completely compatible with the v2.0.0 I intend to publish; the latter will implement another option for displaying property attributes inline (something to the effect of `<W,E,C> property: value`, where `W`, `E` and `C` denote "Writable", "Enumerable" and "Configurable", respectively.

suchipi

Understood :relaxed: no worries. Thank you for your concern, but it's okay if my fork gets out of sync with upstream; I forked because I'll also be adjusting the output format to my preferences, and diff-ability isn't necessary for my use-case (which is embedding this in quickjs-libc's console.log, for use in [suchipi/yavascript](https://github.com/suchipi/yavascript)).