Meteor embraces the community but adding NPM packages for the client is still not easy enough.

What it does

Create meteor packages so you can add them using meteor add just like any other package. Add the NPM package you need and the site will create a browserify:name-of-npm-package for you. Add it to your project and require it using SomeName = Browserify["name-of-npm-package"].

How I built it

Right now it's a proof of concept. This is a meteor app and a node server which does the publication for you.

Challenges I ran into

To do the publication I tried to use a docker (CentOs, Node, Meteor) and upload it to Iron Worker. I got the docker working fine but somehow it didn't work once it was loaded to Iron Worker. Now it's using an ubuntu server on DigitalOcean and it works, but obviously it's not ideal.

Accomplishments that I'm proud of

It was a proof of concept, so I am glad. I am not sure if that's the best solution to use NPM packages in the client, but it is quite easy to use. I have been using manually created packages myself for a time now, so this automatic tool is a step forward.

What I learned

In the not-meteor side of the project, doing shell scripts with node and working with dockers. It was fun. In the meteor part I used my own meteorflux tools to create a fast prototype of the site working.

What's next for meteor-browserify

I am not sure where should it go. If it's a great idea and it should be maintained or not. If the Iron Worker would have worked, it would be super easier to maintain and less complex. I will see if there is any interest in this tool by the community or even MDG. I didn't have time to do a proper UI.

Share this project: