You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@franjaviersans I have created a 1.5.0 release to add a feature you can set glslifyUseCurrentFileAsBasedir to true.
Could you please try this on your side?
I have a relative import in my files like this:
#pragma glslify: someModule = require("../../shaders/utils/someModule.glsl")
And the extension fails to compile like this:
GLSL Lint: GLSL Lint: failed to compile the glslify file! Error: Cannot find module
As it is using only the
basedir
indicated as an option or the working directory path.Is it possible to set an option to solve the import relative to the current file directory?
The text was updated successfully, but these errors were encountered: