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

get-script-tag-vars

v1.1.2

Published

Parse given HTML, look for `script` tags and extract values for given variables.

Downloads

4

Readme

get-script-tag-vars Build Status

Parse given HTML, look for script tags and extract values for given variables.

Intended use case is to help with integration testing server-rendered apps - more specifically, to enable checking variables like __INITIAL_STATE__.

How it works

Uses cheerio to grab all the script tags, parses them with esprima, and then uses estraverse to find variable declarations and assignments. When such a node is found, uses escodegen to generate a string, which is then evaluated with Node's vm.

Usage

This module exports a function, getScriptTagVars. First parameter is the HTML, and the second one is either a string if you only want to check a single variable, or an array if multiple.

const getScriptTagVars = require('get-script-tag-vars')
let html = '<html><script>window.foo=42; var bar="bar"</script></html>'

let foo = getScriptTagVars(html, 'window.foo') // => 42
let bar = getScriptTagVars(html, 'bar') // => 'bar'
let obj = getScriptTagVars(html, ['window.foo', 'bar', 'baz'])
// => { 'window.foo': 42, 'bar': 'bar', 'baz': undefined }

More examples in ./test.js.

Example

const getScriptTagVars = require('get-script-tag-vars')
const assert = require('assert')
const request = require('request-promise-native')

describe('Server-side rendering - initial state', () => {
  it('should have "foo" set', (done) => {
    request('foo/home').then(html => {
      let initialState = getScriptTagVars(html, '__INITIAL_STATE__')
      assert.deepEqual(initialState.foo, {
        foo: 'some value'
      })
      done()
    }).catch(ex => done(ex))
  })
})