-
Notifications
You must be signed in to change notification settings - Fork 76
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
Dependency on @babel/runtime in esm versions #215
Comments
In most cases there is a following portion of code in the top of file.
It looks like building does not happen correctly |
Hmm, thanks for reporting, I will look into this. |
@rohan-deshpande Was the reason for this error ever discovered? I'm encountering the same issue. |
Hi, Was this resolved - or do we have a workaround for this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed in #214
Originally posted by vitalymind July 11, 2022
hi, I am trying to use three-nebula as es module. I assume that after installing npm package "..\node_modules\three-nebula\build\esm" folder should contain pre-built and ready to use library.
However I found following imports that likely should not be there, namely:
7 times
import _defineProperty from "@babel/runtime/helpers/defineProperty";
in files:\three-nebula\build\esm\core\fromJSONAsync.js
\three-nebula\build\esm\initializer\BodySprite.js
\three-nebula\build\esm\initializer\constants.js
\three-nebula\build\esm\initializer\Texture.js
\three-nebula\build\esm\renderer\GPURenderer\Desktop\index.js
\three-nebula\build\esm\renderer\GPURenderer\Mobile\index.js
\three-nebula\build\esm\utils\index.js
1 time
import _objectWithoutProperties from "@babel/runtime/helpers/objectWithoutProperties";
in file\three-nebula\build\esm\initializer\Position.js
From what I understand built three-nebula should not depend on babel, babel used only for building three-nebula it self.
Just to make it clear, minified built version "three-nebula.js" works as expected, no dependency on babel
Can it be fixed?
The text was updated successfully, but these errors were encountered: