-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
webpack compile error on version 1.1.0 #50
Comments
I am pretty sure this is due to us removing the videojs-vr/scripts/rollup-replace.js Lines 8 to 11 in a5cf671
|
Maybe we need to pre-compile threejs into this project on publish so that users don't need to do anything? |
yeah maybe into the cjs and es modules |
…ault export when importing non-module three examples. see issue videojs#50
Hi and thanks for the fast replies, I've done it on my fork on the project, you can check this branch and try in your environment before I make a PR : https://github.com/developpeur2000/videojs-vr/tree/fix-webpack-compilation |
If you have a chance can you try: #53 I think that may fix webpack. I tested it and it appears to work, but I have not worked with webpack that much. |
…ault export when importing non-module three examples. see issue videojs#50
I've left you a comment on the PR because i could not compile videojs-vr without a small change, but once compiled, it fixes the webpack issue 👍 |
…ault export when importing non-module three examples. see issue videojs#50
OK I made the fix and merged it into master, going to cut a patch release |
1.1.1 is out with the fixes, feel free to re-open if its not working. Thanks for reporting, testing, and helping with this issue! |
Hello,
Since version 1.1.0, the module generates warnings and will corrupt the resulting build in my environment (vue-loader/webpack)
to reproduce :
npm run dev
generates no issuenpm install videojs-vr@1.1.0
import 'videojs-vr'
juste before theimport HelloWorld ...
version 1.0.3 is fine, it obviously comes from commit a5cf671 but i'm not a webpack expert enough to find exactly where this comes from
The text was updated successfully, but these errors were encountered: