Strange import error about elliptic HOT 16 CLOSED

What browserify version are you using and what node.js/io.js version?

from elliptic.

This is a browserify/watchify version mismatch problem from my own experience.

from elliptic.

Having the same issue with: browserify ^8.1.3 and watchify ^2.3.0 (node v0.10.36 and io v1.2)
Trying to browserify hapijs/joi

edit see browserify/browserify#1101

from elliptic.

@indutny I had this issue with many browserify / watchify and node version combinations.
Strange thing that only elliptic seems to suffer from this bug.

from elliptic.

@ivan-kleshnin I got you. It is quite odd to see this, since I'm building the dist/ folder contents with browserify (https://github.com/indutny/elliptic/blob/master/Makefile).

I'll look into it over weekend or at Monday.

from elliptic.

Same issue here with elliptic.

from elliptic.

Is there any way to reproduce it?

from elliptic.

same issue here

from elliptic.

It can be reproduced with "browserify": "^8.1.1" and "watchify": "^2.2.1".

Latest of either resolves this issue.

This is not elliptic's fault AFAIK.
On 26 Feb 2015 9:38 pm, "Chevdor" [email protected] wrote:

same issue here

—
Reply to this email directly or view it on GitHub
#30 (comment).

from elliptic.

@dcousens: so is it fixed in browserify now?

from elliptic.

It's a combination thing only. If you just restart watchify it resolves
the issue too.
On 26 Feb 2015 9:43 pm, "Fedor Indutny" [email protected] wrote:

@dcousens https://github.com/dcousens: so is it fixed in browserify now?

—
Reply to this email directly or view it on GitHub
#30 (comment).

from elliptic.

And yes, it is fixed if you use browserify 9.0.0 and watchify 3? (Latest,
whatever that is)
On 26 Feb 2015 9:47 pm, "Daniel Cousens" wrote:

It's a combination thing only. If you just restart watchify it resolves
the issue too.
On 26 Feb 2015 9:43 pm, "Fedor Indutny" [email protected] wrote:

@dcousens https://github.com/dcousens: so is it fixed in browserify
now?

—
Reply to this email directly or view it on GitHub
#30 (comment).

from elliptic.

Cool! Thank you @dcousens . Could you guys please verify this and let me know if it is resolved for you as well?

from elliptic.

@indutny, @dcousens, thanks!
I confirm that with latest browserify / watchify issue is no longer valid.

from elliptic.

Cool, closing! Thank you everyone.

from elliptic.

Same as @ivan-kleshnin
First I had an ancient browserify in my package.json but also karma-browserify was pointing to 8.0.2
Using the latest version of browserify fixed the issue.

from elliptic.