Repository navigation
Conversation
|
Update: added babelify + es2015 to my demo (normal fresnel reflection!—used it to smooth out the control interactions 😄). I still lean toward a build step, but I'll leave the ball in your court on whether to accept/reject. |
|
Hey, If you change the entrypoint to compiled I don't believe this module should be compiled in any form. The application that uses it should take care of that. Your demo looks really cool! |
|
That's fair. 👍 The specific point of failure for me is that |
|
Oh, sorry. I didn't answer your question. Yes, if the entry point is |
See: #8
cc: @nattelog
Long story short, I was unable to use this module out of the box because my project didn't otherwise have any use for a ES6 build step. I could add one, but I generally think it's nicer for a casual dependency not to force it. I apologize for the change in line endings (I can try to undo that if you prefer cleaner git history), but the only changes are:
lib/to.gitignoresrc/to.npmignorelib/indexI know this is an opinionated PR so you're absolutely free to disregard this, no hard feelings; this is just me voicing a preference without just +1'ing the issue. 😄
Thanks for the great module!