Fixing incorrect exports field on package.json

[tornadocontrib]

I have encountered an error while bundling circomlibjs which depends on ffjavascript exports using rollup.js

rollup/plugins#1705

Seems like either ffjavascript has an incorrect exports field defined or the rollup.js couldn't resolve ffjavascript's export definition correctly.

[Kolezhniuk]

@tornadocontrib Hello!
Could you provide more info about that?
We a using exports field on package json to separate builds for NodeJS and Browser
Also we using rollup with other projects which have ffjavascript as dependency
As an example, see

• https://github.com/0xPolygonID/js-sdk
• https://github.com/iden3/js-jwz

[tornadocontrib]

@Kolezhniuk I believe it is because it uses export when the target is nodejs. The examples only use rollup for browser builds.

[Kolezhniuk]

@tornadocontrib One question, why do you need to use rollup for NodeJS?

[tornadocontrib]

@Kolezhniuk Because I would like to bundle the dependency to use it offline without doing yarn install, and to preserve the bundled output with Single executable applications https://nodejs.org/api/single-executable-applications.html

[tornadocontrib]

Fixed by using an older version of ffjavascript though, maybe rollup.js only recognizes old style exports field.