Skip to content
This repository

Added package.json file for npm #2

Closed
wants to merge 2 commits into from

2 participants

Clay Woolam Sébastien Loisel
Clay Woolam
clayw commented May 26, 2012

I have a package that uses some routines from this excellent library as a dependency and wanted to include it in the node package manager to properly automate everything.

Sébastien Loisel
Owner
sloisel commented May 27, 2012

What's happened in the lib subdirectory?

Clay Woolam
clayw commented May 28, 2012

npm wants the package.json to point to the entire compiled JS file located inside the repo

Clay Woolam
clayw commented June 12, 2012

I just rewrote the utils I needed in my own repo so I don't need this as a dependency.... it would still be sweet to see it in the node package manager though. Would you like me to set that up and maintain it?

Clay Woolam clayw closed this June 12, 2012
Sébastien Loisel
Owner

Hi Clay,

Thanks for your comment. I apologize for not following-up on this, I was travelling and writing papers.

The way I've setup my repo is that the lib subdirectory is empty and the library gets built from the source in the src directory using the appropriate build scripts in the tools directory. The versioned libraries are never checked into github.

Similarly, the version number in the package.json file probably ought to be the result of the build scripts. However, I am not sufficiently knowledgeable in node to figure out these changes.

If you could educate me on how this package.json file works, it might be possible to do something.

For example, would it make sense to put a package.json in the src subdirectory that has "version": "XXX" and then get the XXX replaced by a build script using the appropriate version number?

More generally, it's not clear to me how this ties in with the npm "build" procedure.

Thanks,

Sébastien Loisel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.