-
Notifications
You must be signed in to change notification settings - Fork 83
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
glslify will not import (via "require" or "import") #143
Comments
I'm having similar issues I think - pretty sure it's down to this. Some renaming would at least allow to explicitly require the main module file when required. Right now it's completely impossible. |
Thanks homerjam. I'm working on something else all day today, but I'll get this a whirl tomorrow. |
Welp, I tried the fix above, but sadly, it looks like I've got bigger problems. I wasn't able to modify glslify's package.json because glslify never actually installed. I checked my node_modules, and it is not there. Still, npm reported to have installed it without error. Very strange. |
Is there a fix for this? Or has anyone found a suitable workaround? |
Oh, this works: https://github.com/onnovisser/babel-plugin-glsl |
Anyone has ANY fix for this ????? I can't use glslify with typescript and import. That sucks. |
glslify looks great, but I think I might have to go without using glslify until I can solve whatever is going on here.
glslify will not import. Here is what I tried:
No matter what I do, glslify will not import. I get the same errors every time. It's either:
I don't think my setup is too much different from anybody else's. It's just a snowpack build setup with React and Typescript.
Perhaps there was some update in babel or snowpack that broke glslify. I have no idea. Either way, I'm submitting this issue so that it can be out in the public eye, and if I am lucky someone will be able to help me out and post a solution.
The text was updated successfully, but these errors were encountered: