Socket
Socket
Sign inDemoInstall

webpack-glsl-loader

Package Overview
Dependencies
2
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    webpack-glsl-loader

A webpack loader for glsl shaders - includes support for nested imports.


Version published
Weekly downloads
4.3K
decreased by-10.74%
Maintainers
1
Install size
23.6 kB
Created
Weekly downloads
 

Readme

Source

Webpack loader for GLSL shaders

A glsl shader loader for webpack, includes support for nested imports, allowing for smart code reuse among more complex shader implementations. The shader is returned as a string.

Install

npm install --save-dev webpack-glsl-loader

Usage

With require

N.B. As noted in the webpack documentation, you should avoid using this and use the configuration method in the next section.

require('webpack-glsl!./my-lovely-shader.glsl`;

In configuration

{
    module: {
        loaders: [
            {
                test: /\.glsl$/,
                loader: 'webpack-glsl'
            }
        ]
    }
}

and then

require('./my-lovely-shader.glsl`;

On command line

You can also define the module extension bind on the command line if you are not using a configuration file (you probably should be though).

webpack --module-bind 'glsl=webpack-glsl'

Imports

This loader supports an import syntax to allow you to maximise your code reuse and keep those shaders DRY. This syntax is very similar to that of SASS.

Example

Example project structure:

src/
---- js/
---- ---- main.js
---- glsl/
---- ---- includes/
---- ---- ---- perlin-noise.glsl
---- ---- fragment.glsl

If I require my fragment shader inside main.js:

var shader = require('../glsl/fragment.glsl');

I can have that shader include other .glsl files inline, like so:

@import ./includes/perlin-noise;

N.B. all imports within .glsl files exclude the file extension and are relative to the file doing the importing.

Imported files are parsed for @import statements as well, so you can nest imports as deep as you'd like (although, you should probably rethink your shader if you require any more than 2 levels).

Imported files are inserted directly into the source file in place of the @import statement and no special handling or error checking is provided. So, if you get syntax errors, please first check that shader works as one contiguous file before raising an issue.

TODO

  • Deduplicate imports, to prevent code clobbering and conflicts at runtime
  • Make loader file extension agnostic, to allow for you odd people who use other extensions like .vert and .frag.

Keywords

FAQs

Last updated on 21 May 2015

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc