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

be-parsed

v0.0.2

Published

Parse a script tag that contains JSON.

Downloads

10

Readme

be-parsed

Parse a script tag that contains JSON.

Playwright Tests NPM version How big is this package in your project?

<script type="application/ld+json" be-parsed>
{
  "@context" : "http://schema.org",
  "@type" : "Article",
  "name" : "How massive stars in binary systems turn into carbon factories",
  "author" : {
    "@type" : "Person",
    "name" : "Ken Croswell"
  },
  "articleSection" : "The next time you thank your lucky stars, you might want to bless the binaries. New calculations indicate that a massive star whose outer layer gets torn off by a companion star ends up shedding a lot more carbon than if the star had been born a loner. “That star is making about twice as much carbon as a single star would make,” says Rob Farmer, an astrophysicist at the Max Planck Institute for Astrophysics in Garching, Germany. All life on Earth is based on carbon, the fourth most abundant element in the cosmos, after hydrogen, helium and oxygen. Like nearly every chemical element heavier than helium, carbon is formed in stars (SN: 2/12/21). For many elements, astronomers have been able to pin down the main source. For example, oxygen comes almost entirely from massive stars, most of which explode, while nitrogen is made mostly in lower-mass stars, which don’t explode. In contrast, carbon arises both in massive and lower-mass stars. Astronomers would like to know exactly which types of stars forged the lion’s share of this vital element. Farmer and his colleagues looked specifically at massive stars, which are at least eight times heavier than the sun, and calculated how they behave with and without partners. Nuclear reactions at the core of a massive star first turn hydrogen into helium. When the core runs out of hydrogen, the star expands, and soon the core starts converting helium into carbon."
}
</script>

[!Note] It is safest to include these tags before any loading of the be-parsed tag is loaded. No attempt is made to wait for the entire JSON stream to finish loading before parsing what is inside the script tag.

The value of the parsed JSON is available via:

const parsedVal = oScriptElement.beEnhanced.beParsed.value;

Viewing Your Element Locally

Any web server that can serve static files will do, but...

  1. Install git.
  2. Fork/clone this repo.
  3. Install node.js
  4. Open command window to folder where you cloned this repo.
  5. npm install

  6. npm run serve

  7. Open http://localhost:3030/demo/ in a modern browser.

Running Tests

> npm run test

Using from ESM Module:

import 'be-parsed/be-parsed.js';

Using from CDN:

<script type=module crossorigin=anonymous>
    import 'https://esm.run/be-parsed';
</script>