Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish to npm #42

Open
ryanbahniuk opened this issue Sep 16, 2015 · 10 comments
Open

Publish to npm #42

ryanbahniuk opened this issue Sep 16, 2015 · 10 comments

Comments

@ryanbahniuk
Copy link

Are there any plans to publish this to npm in the future?

@DCKT
Copy link

DCKT commented Sep 25, 2015

+1
That can be really nice for application who works around Browserify

@MadLittleMods
Copy link

👍 Official package would be great.

Someone has posted a package with the "MDNs ClassList Polyfill" which is this, Eli Grey's polyfill

@Maximilianos
Copy link

+1

1 similar comment
@selbekk
Copy link

selbekk commented Jan 6, 2016

+1

@sroucheray
Copy link
Contributor

FYI I Just created the pull request #46

@eligrey
Copy link
Owner

eligrey commented Feb 28, 2016

#46 (comment)

@eligrey eligrey closed this as completed Feb 28, 2016
@eligrey eligrey reopened this Feb 28, 2016
@eligrey
Copy link
Owner

eligrey commented Feb 28, 2016

Reopened for now. I will accept a package.json pullreq, but I do not plan on publishing this repo to npm myself. It is up to any of you to be package maintainers for your package manager of choice.

@hpurmann
Copy link

hpurmann commented Aug 12, 2016

Can someone (@tbranyen) publish a new version of this great package to npm? The existing version contains a wrong license text in its license field.

@eligrey Can you update the package.json to a new version and push a corresponding git tag with it? Then @tbranyen is able to publish the new version.

@mcat
Copy link

mcat commented Aug 21, 2017

Looks like NPM is only up to 1.0.1

@nicoabie
Copy link

This npm package contains the latest version of this repo.

I hope someone can update the npm registry because many documentation exists telling users to do npm i classlist.js and the code they get is not the latest nor the most standard compliant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants