Publish on npm

[marvinhagemeister]

Just stumbled on this library and it's amazing, even more so it's gzipped size! my workflow complety revolves around npm and I think I'd be great if NodeList gets published as an npm package.

[gwicksted]

+1

[eorroe]

This sounds good, but I haven't created any modules in npm ever, I only use npm for backend, but if you could do it that'd be pretty awesome, and I'll mention it in the README

[marvinhagemeister]

It's super easy. I think it would be better if you can do it yourself since you as the author should decide on the license and when a new release happens.

https://docs.npmjs.com/getting-started/publishing-npm-packages
https://gist.github.com/coolaj86/1318304

[eorroe]

Honestly not sure if there are going to be new releases, or versioning, since this library does automatic upgrading because it uses the browser that its running on as a dependency. Therefore I don't define my own methods.

If I start making my own methods you got yourself another jQuery sort of.

Only crucial methods like get(), set(), and the item() method, also you have the asArray property (uses a getter instead of a method i.e toArray())

[gwicksted]

I can help publish. Let me know. Bower is another one that would be nice to pull from.

[eorroe]

Sure thing, but that'd be after I make the npm module? (Sorry I haven't created very big applications, that are complex and where I use modules yet, so I don't really use those things, npm, gulp, grunt, bower, etc)

[PeterDaveHello]

If there is versioning, we can distribute this lib over cdnjs 😄

[eorroe]

@PeterDaveHello That's is really awesome, but I'm wondering, why would there be versioning? There won't be anything to break.

I mention in the repo, that this library depends on the browser that it runs on, meaning I won't be breaking anything, if a browser vendor removes the method addEventListener then you can't do:

$$('.child').addEventListener('click', function(evt) {...});

But as we all know addEventListener won't be removed because its Highly used.

So the only deprecation that devs will need to worry about are the ones that browser vendors deprecate (which as I said in the repo, are the ones that are rarely used)

[eorroe]

@PeterDaveHello therefore could it distrubute the latest of NodeList.js?

[PeterDaveHello]

Still can version it to make sure what version we are using, unless you are sure you will never edit the code again, or the versioning will be useful, and latest is not a good method for the cache control, and we don't even know what new features are not in my currently using file, if unfortunately, there is a breaking change, it'll be also hard to confirm that, we don't use it on cdn, even though you don't want it to be hosted on cdn, versioning is still good on my point.

[eorroe]

even though you don't want it to be hosted on cdn

I do want it hosted on cdn (that's why I said awesome)

Now question: Could it be versioned on the cdn? Where let's say v1 of NodeList.js on cdnjs

cdnjs keeps its own version, instead of myself

I believe that's what you mean by?:

Still can version it to make sure what version we are using

[PeterDaveHello]

Could it be versioned on the cdn? Where let's say v1 of NodeList.js on cdnjs
cdnjs keeps its own version, instead of myself

Yes, but I wanna make it consistent with official repo, it'll be better if we host it.

[eorroe]

make it consistent with official repo

What do you mean? as in I never update the repo?

it'll be better if we host it

Just the current version, or the whole project? (really confused, please elaborate)

[PeterDaveHello]

What do you mean? as in I never update the repo?

I meant not let cdnjs keeps its own version, that's why we need versioning, v0.0.1 is always v0.0.1, no matter it's on official GitHub repo or on cdnjs 😄

Just the current version, or the whole project? (really confused, please elaborate)

We only host the files that browser will need to use, not the whole project, let's take foundation-essential as an example.

[eorroe]

Crap I really don't wanna version though, as I feel as if when theirs a version number behind it, an update is expected.

You said only way is if I will never touch the code again

But I can't guarantee that, I can't think of something that the library really needs added, but they may be something someone comes up with, but majority of it will be things that they can simply implement on their own that is not needed. (So your answer would probably be that's why you version it 😆 , but yea really don't want to version it)