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

netsuite-testing

v1.0.10

Published

Module to simulate SuiteScript functions for testing purposes

Downloads

14

Readme

Netsuite-Testing

This will help testing of SuiteScript scripts

In order to make this work, you need to copy the contents of this into your project's node_modules directory.

I also use the following node modules:

  • app-module-path
  • amd-loader

Here is a sample test script:

var path = require('path')
require('app-module-path').addPath(path.join(__dirname, '..')) // adds project dir (running from @/test)
                                                               // to path, to use my custom module
const expect = require('chai').expect
if (typeof define !== 'function') { require('amd-loader') }
const Beebole_Customer_CS = require('../FLX_Beebole_Customer_CS.js')

describe('/Beebole_Customer_CS', function (done) {
  // Instantiate our module, passing in our dependencies
  var button = { isDisabled: true }
  const currentRecord = {
    getValue: function (a) {
      return a.fieldId
    },
    getField: function (id) {
      return button
    }
  }
  it('pageInit should enable button', function (done) {
    Beebole_Customer_CS.pageInit({ currentRecord: currentRecord })

    // Perform assertions
    expect(button.isDisabled).to.equal(false)
    done()
  })
})