Officially adding Zepto to NPM

[ChrisAntaki]

I just reached out to the NPM support team, and we freed up the zepto name.

Would your team like to help make zepto CommonJS compliant for use with browserify and webpack? And perhaps take over the npm module?

[AlexBai1991]

same feeling

[Florian-R]

https://github.com/madrobby/zepto#help-it-doesnt-work-in-browserify

[mislav]

and we freed up the zepto name.

How is it "freed up", when there's a package published under "zepto" name by somebody called Brian?

[ChrisAntaki]

npm transferred the module to my account, chrisantaki, I just haven't uploaded a new version yet so it's showing the old author.

[ChrisAntaki]

@mislav I definitely understand your position, back when CommonJS was used mainly on the server side in 2011. The landscape has evolved greatly since then though. https://github.com/webpack/webpack has 10,859 stars, https://github.com/substack/node-browserify has 8,894 stars, and https://github.com/babel/babel has 12,489 stars. More people are building static client side applications, with a separate API layer in Heroku, AWS, etc.

https://www.npmjs.com/package/zepto is getting 198 downloads a day on npm, with a 3 year old version. Imagine how many people might be downloading an up-to-date version, especially if it were compliant with CommonJS? Would you want myself and a buddy to help add CommonJS support?

[mislav]

I would be grateful if you handed over npm ownership to ~mislav and ~thomasfuchs so we can maintain the package.

We can't promise CommonJS support, but we can certainly publish compiled zepto.js as-is.

[ChrisAntaki]

Awesome! I'll reach out to npm support

[mislav]

I'll reach out to npm support

If you own the "zepto" package right now, you can add us without the help of npm support.

Note that after we take over the package, we will remove you as admin of the package to restrict publishing of "zepto" only to maintainers. I hope you will understand. Thanks!

[ChrisAntaki]

If you own the "zepto" package right now, you can add us without the help of npm support.

Coolio, I will push a new version and then add you two as collaborators.

Note that after we take over the package, we will remove you as admin of the package to restrict publishing of "zepto" only to maintainers. I hope you will understand. Thanks!

Of course 😄

[ChrisAntaki]

Just added you two, please let me know if I can help any further.

[ChrisAntaki]

Sidenote: Instead of full CommonJS support, you could advise people to simply require('zepto') or import 'zepto' once, defining $ globally.

[mislav]

Thanks! Takeover complete 👍

[ChrisAntaki]

Great, glad your team is running it now 😎

[ChrisAntaki]

@bhurlow thanks for being flexible about releasing the npm module 😄

[EskelCz]

"Zepto - in the process of being transferred to maintainers"
It's been five months. What happened to the official npm release? :(

[ChrisAntaki]

They successfully took over the NPM package about 5 months ago. They still have to push an update before the page shows them as the new owners. The package no longer shows up in my list of packages though: https://www.npmjs.com/~chrisantaki

[ChrisAntaki]

I have a feeling this project doesn't get updated much anymore.

[mislav]

We haven't had a release since then. When we eventually have a release, we will update the npm package. Patience! 😉

[themadcreator]

Any update on the npm package now that you've owned it for well over a year?

Several alternative commonjs compatible zepto wrappers have popped up on npm since the last comment [0-3], most of which are out of date and pollute the landscape.

Please please pretty please release a commonjs compatible npm package.

[0] https://www.npmjs.com/package/npm-zepto
[1] https://www.npmjs.com/package/zepto-modules
[2] https://www.npmjs.com/package/commonjs-zepto
[3] https://www.npmjs.com/package/zepto-commonjs