Publish to npm?

[paulyoung]

I'd like to create something that depends on Framer.

[koenbok]

Sure. I don't see why not :-)

[koenbok]

Here you go:

https://www.npmjs.org/package/framerjs

[paulyoung]

👍

[paulyoung]

When I require('framerjs') I get Error: Cannot find module 'framerjs'.

[paulyoung]

So, this is due to the build directory not being submitted as part of the package.

@koenbok - could you make that happen?

[paulyoung]

Actually, Bower might be better for this. At least having a component.json file would let me try that out.

[paulyoung]

@koenbok - wondering if you'd mind following up here.

[zanona]

As of v3.0.0 the build/frame.js file is not included making it impossible to depend on the framejs via npm? Perhaps this issue should be re-opened?

[jchavarri]

@zanona @paulyoung You can build automatically after installing, using the scripts key on your package.json:

"scripts": { "postinstall": "cd ./node_modules/framerjs && make" }

[jacobbubu]

I think this issue should be reopen due to the lack of compiled version of framerjs,

[koenbok]

I keep them here: http://builds.framerjs.com/

But I don't like keeping them in git because you get huge nonsensical diffs.

[jacobbubu]

You don't need to put the compiled version into git like you did already (add build file in .gitignore).
Just add { “republish”: ‘make’ } to scripts field in ‘package.json’ and change the main filed to ./build/framer.js. And then I also recommend that moving most of the dependencies that used for build and test into ‘devDependencies’. That makes more npm friendly and save a lot of for npm install.

[koenbok]

Ok let's do it.

[paulyoung]

For my own projects, I've followed similar steps to those outlined here: http://mammal.io/articles/using-es6-today/#publishing-to-npm

[jperals]

Hi there, any update about this? @jacobbubu's proposal seems quite straightforward to implement (with the required change that the republish task should be "make release" instead of just "make", I think). I could provide a PR myself —unless now there is any reason against doing this @koenbok? (I guess not as this issue is still open)

PS: actually, the main field in package.json points to lib/Framer.js which doesn't exist, even after building? That doesn't make sense anyway, right?, or am I missing something?

[eelco]

Hey @jperals, Framer doesn’t have semantic versioning, which makes it not so nice to work with in combination with npm. It’s (therefore?) not a popular use case either, making this issue very low priority. The main field is indeed outdated.