-
Notifications
You must be signed in to change notification settings - Fork 47
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
support npm #30
Comments
I also wish it!! |
+1 |
The addition of this package to npm would be greatly appreciated. As of today most packages live on npm which makes them in credibly easy to pull down during build scripts as well as in general development. I'd be happy to help with this if the maintainers aren't interested. |
+1 |
1 similar comment
+1 |
I think it's time to get the thing done. How should we proceed ? Should we create a simple NPM implementation (with a package.json) or should completely move to the NPM architecture (splitting the file into smaller one etc) ? |
@ValentinTrinque I think it's a pretty simple process: https://docs.npmjs.com/getting-started/publishing-npm-packages Add a package.json file with pertinent information, create a user if you don't already have one, and run |
I just opened a PR that gets the package.json file set up for publishing to alleviate the first step of what I said above. #39 Once merged you should be able to create a user like the link I outlined and then publish it. |
That's nice. I will look into that. |
Any chance we can get this accomplished today? I'm working on starting a new project that could really benefit from this. |
I would like to, however I am only a fresh new collaborator and the creation of the nam account should be created by stretchr.
Valentin Trinqué
Software developer
France
|
@matryer Any chance you could get this going for us? |
@matryer I see that this package is still not published to npm. We've moved a copy of this into our private npm registry and publish there so it can be pulled down during build processes, but it would be greatly appreciated if we could get this accomplished. The name of the package would have to change as there is already an |
can you support npm package and work with webpack?
thinks
The text was updated successfully, but these errors were encountered: