Export `WebVRPolyfill` as standalone module about webvr-polyfill HOT 7 CLOSED

à la es6-promise, this is what I'd recommend:

// es6 import
import { WebVRPolyfill } from 'webvr-polyfill';
WebVRPolyfill.polyfill();

// require
const WebVRPolyfill = require('webvr-polyfill');
WebVRPolyfill.polyfill();

from webvr-polyfill.

This isn't fixed. Why is this closed?

from webvr-polyfill.

I thought I had fixed it, but you're right!

from webvr-polyfill.

Currently you can access the WebVRPolyfill object in built environments (browserify, webpack, etc.) via

// es6 import
import { WebVRPolyfill } from 'webvr-polyfill/src/webvr-polyfill';
// require
const WebVRPolyfill = require('webvr-polyfill/src/webvr-polyfill').WebVRPolyfill;

The use case of dropping in the script file should just seemlessly polyfill the API (which is what bundling from src/main.js does), and any custom configuration (beyond the WebVRConfig values) where you'd want to access the polyfill constructor directly can be done by accessing the constructor via require/es6 imports. Is there a common use case inbetween these two scenarios?

from webvr-polyfill.

I started a local branch on this. Is there interest in it? (I've been modelling it after es6-promise.)

from webvr-polyfill.

I'd just be hesitant to do any big architectural changes without first having some solid testing, and that the script in build/ still just auto-polyfills without further interaction, and if the imports work from #47 (comment), I'd be curious what is missing (in lieu of larger changes)

from webvr-polyfill.

Fixed in 0.10.0

from webvr-polyfill.