-
Notifications
You must be signed in to change notification settings - Fork 21
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
Error on __dirname #18
Comments
how are you using this ? |
@calvinmetcalf |
is it being included in your rollup configs ? |
@calvinmetcalf what do you mean? Error disappears since I remove |
this is a plugin for rollup, depending on your config when building your thing it may or may not be included in your build and thus error out |
UPDATED: @calvinmetcalf , |
put globals before resolve in your config
…On Fri, Oct 5, 2018 at 9:39 AM Alexander Kurakin ***@***.***> wrote:
@calvinmetcalf <https://github.com/calvinmetcalf> , build.js
<https://gist.github.com/kuraga/6da398ce6cadefc4a3552a7bb255f929>,
package.json
<https://gist.github.com/kuraga/27c3321e3ea637c60ac138f48a633ee7>. And: import
tman from 'tman'; tman.run();.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABE4n6I0_OZ1Lr0cru9KIkJwi8ox9PDEks5uh2EBgaJpZM4XJUbJ>
.
|
@calvinmetcalf , then:
But it does... |
@calvinmetcalf Hm, interesting facts (on original code):
|
@calvinmetcalf but what does this error mean? Where does it come from? The error. Forget the context. |
the original error has to do with it not being able to find the stand in module we use for __dirname, not sure why... |
@calvinmetcalf , got part of this issue.
So, you were right:
But this plugins order is incompatible (in my code) with ESM... And ESM works fine without your plugin. |
@calvinmetcalf ahaha, I got it!!! We have a new error since I set correct plugins order. See #20 , please! |
Null byte ( |
Ah, ok, close in favor of #23 . |
Any thoughts?
The text was updated successfully, but these errors were encountered: