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

wsf2json

v1.0.5

Published

Windows Script File (WSF) to JSON converter (including code parsing)

Downloads

21

Readme

Windows Script File (WSF) to JSON converter

With this tiny utility you can parse Windows Script File (WSF) into a json file. Scripts reference inline will be included. Further more, it will also attempts to resolve all the "src" referenced files and includes their script in "value" strings.

Assuming a simple wsf with below content:

<?xml version="1.0" ?>
<?job error="true" debug="true" ?>
<package>
    <job id="job1">
        <runtime>
            <named helpstring="Enter the Script to exeucte" name="script" />
        </runtime>
        <script language="VBScript" name="script" >
            Dim script
            'Read and assess the parameter supplied
            if WScript.Arguments.named.exists("script") Then
                WScript.Echo "Argument received: " + WScript.Arguments.named("script")
                script = WScript.Arguments.named("script")
            Else
                WScript.Arguments.ShowUsage
                WScript.Quit
            End If
        </script>
        <script language="VBScript" src="scripts\FS.vbs" />
    </job>

    <job id="job2">
        <script language="VBScript" >
            Wscript.Echo "We are in Job2"
        </script>
    </job>
</package>

The generated JSON would be:

the responding output jscript file is like :

[
  {
    "id": "job1",
    "runtime": [
      {
        "name": "script",
        "helpstring": "Enter the Script to exeucte"
      }
    ],
    "script": [
      {
        "language": "VBScript",
        "type": "inline",
        "value": "\r\nDim script\r\n'Read and assess the parameter supplied\r\nif WScript.Arguments.named.exists(\"script\") Then\r\nWScript.Echo \"Argument received: \" + WScript.Arguments.named(\"script\")\r\nscript = WScript.Arguments.named(\"script\")\r\nElse\r\nWScript.Arguments.ShowUsage\r\nWScript.Quit\r\nEnd If\r\n"
      },
      {
        "language": "VBScript",
        "type": "src",
        "src": "scripts\\FS.vbs",
        "exists": false
      }
    ]
  },
  {
    "id": "job2",
    "runtime": [],
    "script": [
      {
        "language": "VBScript",
        "type": "inline",
        "value": "\r\nWscript.Echo \"We are in Job2\"\r\n"
      }
    ]
  }
]

Usage

parse a wsf file by path

const {parseWSF} = require('wsf2json');

let wsfPath = __dirname + '/test.wsf';
parseWSF(wsfPath).then((jobs)=>{
    console.log(JSON.stringify(jobs, null, 2));
}).catch((error)=>{
    console.error(error)
})

(Or) if the content is available in string, simply pass it to String parser

const {parseWSFStr} = require('wsf2json');
let xml =`<?xml version="1.0" ?>
    <?job error="true" debug="true" ?>
    <package>
        <job id="job3">
            <runtime>
                <named helpstring="Enter the Script to exeucte" name="script" />
            </runtime>
            <script language="VBScript" name="script" >
                Dim script
                'Read and assess the parameter supplied
                if WScript.Arguments.named.exists("script") Then
                    WScript.Echo "Argument received: " + WScript.Arguments.named("script")
                    script = WScript.Arguments.named("script")
                Else
                    WScript.Arguments.ShowUsage
                    WScript.Quit
                End If
            </script>
            <script language="VBScript" src="scripts\\FS.vbs" />
        </job>
        <job id="job4">
            <script language="VBScript" >
                Wscript.Echo "We are in Job2"
            </script>
        </job>
    </package>`
    
parseWSFStr(xml).then((jobs2)=>{
    console.log('parsing wsf content:')
    console.log(JSON.stringify(jobs2, null, 2));
}).catch((error)=>{
    console.error(error)
})

Finally, to extract vbscript components (both inline & src reference content) into a string, call below method passing the parsed wsf json.

const {parseWSF, extractVBS} = require('wsf2json');

let wsfPath = __dirname + '/test.wsf';
let wsfJson = await parseWSF(wsfPath);
let vbs = extractVBS(wsfJson);
console.log('\r\nextracted vbs from wsf file')