Closed msridhar closed 10 years ago
Well, if you depend on 0.3.x, depend on 0.3.x! The version was bumped because there's potentially breaking changes!
Also, getting that error shows that something went wrong earlier in the install process.
I'd love to know if your code breaks on 0.4.x, but '*' dependencies are wrong, always. 0.x is unstable anyway, but in general, you can't depend on it that way and have it stay working. HTML5 is a semver module.
Let me know if you need me to dive in further; I'll reclose this if I don't hear back later.
Oh! The main entry point was moved in that last merge. There's a new entry point, but it's definitely not backward compatible. You'll need to fix your deps against 0.3.x if you want to keep that interface.
Hi, we'll fix our dependence at 0.3.x for now then, thanks! I'll also look into how the interface has changed.
Awesome. And thanks for the heads up that v0.4.0
was missing its main entry point. Total doh moment there.
Our rewriting-proxy project depends on html5. When doing a fresh install today, which pulled v0.4.0 of html5 from npm, even the following simple code doesn't work:
The package.json just has:
When I run the above code, I get:
Asssuming this is in fact a bug, can it be fixed soon and a new version pushed to the npm registry? If not, we'll have to push a new version of our package that depends on 0.3.x. Thanks!