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

@thibka/postprocessor

v1.0.3

Published

Makes Three.js postprocessing management easier.

Downloads

7

Readme

PostProcessor

Makes Three.js post-processing easy. Depends on postprocessing 5.0.0 and above. This is a WIP.

Install

npm i three postprocessing
npm i @thibka/postprocessor

Usage

The PostProcessor composer must be used instead of the classic Three.js renderer.

import PostProcessor from './js/PostProcessor.js';

// render loop
function render() {
    requestAnimationFrame(render);
    PostProcessor.composer.render(); // here
};

// resize function
function resize() {
    canvas.width = window.innerWidth;
    canvas.height = window.innerHeight;

    PostProcessor.composer.setSize(canvas.width, canvas.height); // and here
    camera.aspect = canvas.width / canvas.height;
    camera.updateProjectionMatrix();
}

// Initialization.
// If no pass is added, the PostProcessor will simply render the scene with no effect.
PostProcessor.init(scene, camera);

Then, post-processing passes can be added or removed dynamically

PostProcessor.add('bokeh', 
    {   focus: .9, 
        dof: 0, 
        aperture: 0.1, 
        maxBlur: 1  });

PostProcessor.remove('bokeh');

// Default parameters will be used if none is provided
PostProcessor.add('pixelation');

Glitch

PostProcessor.add('glitch', 1); // 1 is the default noiseMapSize parameter
PostProcessor.remove('glitch');

Scanlines

PostProcessor.add('film');
PostProcessor.remove('film');

SMAA Antialiasing

The SMAA Effect needs these two images to work.

Simple call

// First you must load the two "search" and "area" png images. Then use them this way:
PostProcessor.add('smaa', {
    imgSearch: smaaSearchImage,
    imgArea: smaaAreaImage
});

Using @thibka/multiloader

You can also use the multiloader to easily load the two images before using them.

MultiLoader.load({
    files: {
        // ...
        smaaSearch: { 
            type: 'image', 
            path: require('./img/smaa/smaa-search.png')
        },
        smaaArea: { 
            type: 'image',
            path: require('./img/smaa/smaa-area.png')
        }
    },
    onFinish: init
});

// ...

function init() {
    PostProcessor.add('smaa', {
        imgSearch: MultiLoader.files.smaaSearch.image,
        imgArea: MultiLoader.files.smaaArea.image
    });
}