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

safeload-yaml-pmb

v4.210519.0

Published

Re-export my current favorite safe YAML loading function. Bridges the gap between js-yaml v3 and v4.

Downloads

418

Readme

safeload-yaml-pmb

Re-export my current favorite safe YAML loading function. Bridges the gap between js-yaml v3 and v4.

API

This module re-exports the safeLoad or load function from js-yaml, depending on which of them is safe to use for loading YAML.

Why?

Unfortunately, js-yaml v3 had an unsafe load function, so you had to remember to use the safeLoad function to explicitly opt-out of madness.

In v4, the developers have learned from their past API design mistakes, and the load function is now safe by default.

However, to make sure everyone knows they fixed it, they made another problematic API design choice: The safeLoad function now throws an error, telling you it's deprecated and you should use just load.

Thus, you now have a double-edged sword:

  • If you use the load function, and for whatever reasons your require() happens to use js-yaml v3, your program is insecure.
  • If you use the safeLoad function, and for whatever reasons your require() happens to use js-yaml v4, your program fails to load the file data.

In an ideal world, you could ensure that your program is only ever invoked in an environment in which require('js-yaml') will pick v4 or later. In the real world, I need a reliable and robust fallback.

Known issues

  • Needs more/better tests and docs.

 

License

ISC