parro-it / awesome-micro-npm-packages Goto Github PK

I see the Other section, but I don't think utils are exactly "Other" thing.

Hi,

the node-uuid package is now just uuid, as you can see here.

I think it's better to just call id uuid to avoid people mistakenly installing the deprecated node-uuid. Does this make sense?

Anyway, good job!

http://nightly.changelog.com/2017/09/25/

:)

Studying through the readme, I found two links that are not working anymore:

• Build small single purpose modules
• Why I think "micro-packages" are a good thing.

For the first one, I tried to search on google and also retrieving from web.archive.org but with no success in that.

The second, I found this article, but someone needs to verify that it's the same as the one linked earlier.

Any ideas on how to fix this?

I would like to suggest adding the package size to each line.

It could just simply be a badge that gets the size in real time, see Package Phobia.

For example:

• is-sorted - A small module to check if an Array is sorted.
• array-first - Get the first element or first n elements of an array.

@parro-it Thoughts?

The bug is fix

Aaargh! I accidentally deleted this repo while submitting it to awesome.
Fortunately, I saved a copy of the list on my dev machine...
I will rewrite all other files, but commit history, stars and watchers are definitely lost 😢
So sorry with all the watchers...

Hi people!
If you are watching this repo in order to learn new JS stuff,
you may like my new project: 🐱amaj🐱.
I'll respond there to technical questions regarding JavaScript.

I was thinking of adding quetie (a very small queue implementation) here, but I wasn't sure what section it should go in. It's implemented using arrays so maybe that section?

Otherwise, maybe a new data structures section? Might be nice to collect all the small implementations 😄

Would you be opposed to re-organizing the sections and lists by alphabetical order? As the list grows it will be easier to scan for information.

I'd be happy to do a PR

I think lagden-promisify is a good addition to the list under the 'Promise' section. It doesn't depend on a Promise library like thenify does thus it's more lightweight. Should I add it besides thenify or replace thenify?

If added besides thenify I think the description should be clear about the difference between the two. Thoughts?