post new learn resources about "package publish"

[AugustinMauroy]

#36

[AugustinMauroy]

cc @JakobJingleheimer

[JakobJingleheimer]

🙌

[JakobJingleheimer]

Is "We gotchu" too colloquial (difficult for ESL users)? Should it be "We got you"?

[AugustinMauroy]

Is "We gotchu" too colloquial (difficult for ESL users)? Should it be "We got you"?

Any strong opinion on that. Because blue sky have an integrated translation feature (google translate) and I had test with "we gotchu" and it's translate correctly.

And also I think we need to be familiar instead of corporate

[JakobJingleheimer]

blue sky have an integrated translation feature (google translate) and I had test with "we gotchu" and it's translate correctly

Sweet! Looks like no problem then 😃

[marco-ippolito]

From the guidelines https://github.com/nodejs/bluesky/blob/main/review_guidelines.md it seems only release annoucements are allowed. Let me check if documentation needs to be updated. (I see other things have been reposted so apparently the documentation is wrong)

Apparently its ok to repost articles

[bmuenzenmeyer]

From the guidelines https://github.com/nodejs/bluesky/blob/main/review_guidelines.md it seems only release annoucements are allowed. Let me check if documentation needs to be updated. (I see other things have been reposted so apparently the documentation is wrong)

I didn't know this either, and have been asking for many reposts. agree we should update

[AugustinMauroy]

@nodejs/bluesky can we process for this pr ?

[AugustinMauroy]

re ping @nodejs/bluesky

[joyeecheung]

The article itself doesn't seem to be ready as a definitive guide for package publishing, I've seem some package maintainers discussing the usage of exports field for various special needs outside what's described in that article (e.g. patterns used by https://github.com/privatenumber/pkgroll). It would be better to be sent as an invitation for further improvement on this guide instead of saying "we gotchu" which implies it's everything you will need.

[JakobJingleheimer]

The article itself doesn't seem to be ready as a definitive guide for package publishing, I've seem some package maintainers discussing the usage of exports field for various special needs outside what's described in that article (e.g. patterns used by https://github.com/privatenumber/pkgroll). It would be better to be sent as an invitation for further improvement on this guide instead of saying "we gotchu" which implies it's everything you will need.

That is a good point: it is not in its final form (ex 2 items down my todo list is splitting this article into 2: basic and exotic configs).

Happy to re-word.

[joyeecheung]

Does the new wording change it much? I feel that it would be more apt to say something like "we have started working on this guide, com join us improving it", to make it clearer that it's not complete.

[JakobJingleheimer]

How about

Trying to publish a package and there are just. so. many. options? The good news is it's probably not as complicated as it seems.

We've started a guide that covers common use-cases (and some exotic ones); it doesn't cover everything yet—additions welcome!

https://nodejs.org/en/learn/modules/publishing-a-package

[joyeecheung]

Generally LGTM though I think

additions welcome!

can probably be tweaked to

if you see anything that's worth updating, click that "Edit this page" link and submit a PR!

to be more actionable (does it fit in 300 chars?)

[JakobJingleheimer]

Sounds good to me. I'll try to get it to fit

[AugustinMauroy]

Any news ? Do we still need a post for that ?

[joyeecheung]

I think it's just pending an update based on #44 (comment)?

[AugustinMauroy]

cc @joyeecheung

[JakobJingleheimer]

Ack. I didn't open this, so it wasn't listed in my PRs so I forgot about it. Thanks Augustin and Joyee!

[joyeecheung]

LGTM though it seems missing a punctuation