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

try-catch-loader

v1.0.2

Published

A Webpack loader that wraps required JS in a try/catch.

Downloads

11

Readme

try-catch loader

A Webpack loader that wraps required JS in a try/catch.

Why would I use that?

Some client-side JS libraries don't like being loaded on the server - ones that do something like check navigator.userAgent when loading, for example. This causes problems when you're trying to do server-side rendering of a React component (for example) as the require statement will fail.

What doesn't it do?

Fix the library. It'll just cause the require statement to return null, so the module will be inaccessible. You either need it to be inside a function that doesn't get run on the server, or wrap it in an if statement that checks what it is.

Give me an example

Fine. Consider the following React component:

var someClientsideLibrary = require('some-client-side-library);
var React = require('react');

module.exports = React.createClass({
    render: function() {
        return <div>Hello.</div>
    },
    componentDidMount: function() {
        someClientsideLibrary.doThing(this.findDOMNode());
    }
})

If someClientsideLibrary uses document, navigator, window etc. on load it will break any attempt at server-side rendering of this component. When wrapped in try-catch it won't - it will just return null. Normally that would be a problem, but server-side rendered React components never run componentDidMount (instead running it client-side on load), so the render won't actually throw an error.

How do I use it?

Glad you asked. I recommend not hard-coding this in your webpack config, as try/catching every library will add a performance penalty. Instead, add it in the require statement, like so:

require("try-catch!a-troublesome-library");

Then submit a pull request to that library with a suggestion on how to make it server friendly (like, moving the use of window to the first time the library is used rather than when it is loaded).