Name		Name	Last commit message	Last commit date
parent directory ..
src		src
.babelrc		.babelrc
README.md		README.md
package.json		package.json
webpack.config.js		webpack.config.js
yarn.lock		yarn.lock

README.md

babel-plugin-glslify

This workspace makes use of a pretty bare bones webpack setup with babel and babel-plugin-glslify.

The compositions under test here are:

No.	Method	Command	File	Yes/No?
1	glslify``	`yarn start:inline`	./src/glsl-inline.js	½
2	glslify('./file.glsl')	`yarn start:file`	./src/glsl-file.js	✔
3	glslify(/* shader string */)	`yarn start:import`	./src/glsl-import.js	✘

Issues

1. Inline with variable(s)

Currently when using a tagged template literal with a variable within it, the compiler will error. I'm still working through whether this is a babel tagged template expression issue or an issue with glslify.

3. Shader string

Importing both the vertex and fragment shaders in via require|import and then parsing those using glslify() method throws an error. I'm not sure if this is expected behaviour (i.e. it only expects a shader file path) or if the method is capable of parsing the shader string directly.