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

@rubenrodriguez/esbuild-plugin-glslify

v1.0.1

Published

glslify plugin for esbuild. both inlined template tags or standalone imported files.

Downloads

5

Readme

esbuild-plugin-glslify

An esbuild plugin to compile glslify shaders. Both standalone files and inline template tags are offered.

I was finding errors with other glslify plugins, but found that when using the glslify tools directly everything worked as expected. This tool is based on how things are managed in the glslify cli.

Usage

Install: npm install @rubenrodriguez/esbuild-plugin-glslify

Import and use the package that suites your project.

import { glslifyFiles, glslifyInline } from './index.mjs'
import { build } from 'esbuild'

await build({
  entryPoints: ['example/input.mjs'],
  outfile: 'example/output.js',
  target: 'es6',
  bundle: true,
  format: 'esm',
  plugins: [
    glslifyFiles(),
    glslifyInline(),
  ],
})

Example

There is an example esbuild config, which references an input javascript file which imports a .vert shader, and also has the same contents as an inline shader. The output shows that they export the same thing. I was specifically getting errors with other loaders using glsl-georender-style-texture and the way that the package imports the same package twice. Once from the root shader, and another time from within another dependency. Other glslify packages would represent the same struct with two different names, one per import. This package gives the correct result.

Exports

glslifyFiles accepts an object of options { fileTypes }, where fileTypes is an array of the relevant file extensions to glslify on import.

glslifyInline accepts an object of options, { templateTag, fileTypes }, where templateTag is a string that represents the template tag. This defaults to glsl as is common in this ecosystem. fileTypes is an array of the file types to look for this templateTag in.