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

glsl-preview

v1.4.6

Published

Live preview fragment shaders in the current editor with `ctrl-shift-G`.

Downloads

5

Readme

GLSL Preview package

Live preview fragment shaders in the Atom editor, with ctrl-shift-G.

Make sure you install language-glsl for syntax highlighting.

Uniforms

The following default uniforms are included, no need to add these into your fragment shaders. Uncheck Include default uniforms in the package settings to declare these yourself.

uniform vec2 iResolution; // size of the preview
uniform vec2 iMouse; // cursor in normalized coordinates [0, 1)
uniform float iGlobalTime; // clock in seconds

The variants u_resolution, u_mouse and u_time can also be used to match the style found in The Book of Shaders.

Textures

Textures can be loaded by defining a uniform with a comment containing the path to the file. The syntax is:

uniform sampler2D <texture_name>; // <path_to_file>

For example:

uniform sampler2D inThisDirectory; // foo.jpg
uniform sampler2D inOtherDirectory; // ../other_textures/bar.png
uniform sampler2D withAbsolutePath; // /Users/ford/textures/blah.bmp

Shader errors

If the shader fails to compile, the tab and line number will subtly highlight in red.

If enabled in the package settings, a notification will show the error message:

Capture images

Right click on the preview to copy or save a still image of the shader. This can also be done by running the command "Glsl Preview: Copy Image" or "Glsl Preview: Save Image" from the command palette (cmd-shift-P).

Examples

Example shaders can be found in the examples/ directory.

glslify

Supports glslify for importing glsl modules.

// Import from local file:
#pragma glslify: map = require('./map')

// Import from npm installed module:
#pragma glslify: rainbow = require('glsl-colormap/rainbow')

Frag snippet

Create a new .glsl file, type frag, and hit enter. This will output the base fragment shader code to get started from.

Credits

Markdown Preview for the boilerplate code.

three.js for simplifying WebGL.