WESL enriches the WGSL shader language with extensions like import, @if.
wesl-js has tools and libraries for JavaScript / TypeScript projects to use WESL.
Linking .wesl and .wgsl files for WebGPU
TBDAdd the vite wesl plugin to your bundler's configuration:
/// vite.config.ts
import type { UserConfig } from 'vite'
import viteWesl from "wesl-plugin/vite"; // plugins are avalable for esbuild, rollup, webpack, etc.
export default = {
plugins: [ viteWesl() ], // <- add wesl plugin
} satisfies UserConfig;how to add plugin
lowering binding structs
reflection
Linking .wesl and .wgsl files.
analogous to esbuild for .js and .ts.
As with other programming languages, module linking becomes useful when your WGSL code grows large enough to be split into separate reusable files. Linking integrates the code modules together while solving for:
- renaming - Two functions with the same name? The linker will rename one of them, and rewrite all the calls to the renamed function.
- deduplication - Two modules import the same function? You get only one copy.
- recursion - Importing a function that references another import? You get all references, recursively.
- dead code - Importing a function from a big module? You get only that function and its references, not the whole file.
esbuild, rollup, etc.
provide your own list of shader strings.
See also wesl-rs for using WESL in Rust/C++ projects. wesl-rs and wesl-js are interoperable implementations of the same WESL specification.
See Developing for working on wesl-js itself
Except where noted (below and/or in individual files), all code in this repository is dual-licensed under either:
- MIT License (LICENSE-MIT or http://opensource.org/licenses/MIT)
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.