npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

navinfo-webpack-glsl-loader

v1.0.0

Published

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

Downloads

3

Readme

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('navinfo-webpack-glsl-loader!./my-lovely-shader.glsl');

In configuration

{
    module: {
        loaders: [
            {
                test: /\.(vs|fs|glsl)$/,
                loader: 'navinfo-webpack-glsl-loader'
            }
        ]
    }
}

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.glsl;

N.B. all imports within .glsl files include 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