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

@factorial/stack-javascript

v0.8.1

Published

This is the JavaScript plugin for `@factorial/stack-core`.

Downloads

644

Readme

@factorial/stack-javascript

This is the JavaScript plugin for @factorial/stack-core.

It adds

Installation

You can install it via:

yarn factorial init

or manually via:

yarn add @factorial/stack-javascript

Make sure it is added to your .factorialrc.js like this:

// .factorialrc.js

module.exports = {
  use: [require("@factorial/stack-javascript")],
};

And add a .eslintrc.js:

// .eslintrc.js

module.exports = {
  root: true,
  extends: [
    require.resolve("@factorial/stack-javascript/eslint"),
  ],
};

Available configurations:

  • @factorial/stack-javascript/eslint: Default configuration, includes base, jsdoc and jest
  • @factorial/stack-javascript/eslint/base: Basic linting rules, always necessary
  • @factorial/stack-javascript/eslint/jsdoc: JSDoc linting
  • @factorial/stack-javascript/eslint/jest: Jest test spec linting

Defining the output format

By default the output format of the build files is determined by the defined targets (see main README).

If you want to explicitely define it (for example to make sure the build files are ES modules), you can do that by passing a configuration object:

// .factorialrc.js

module.exports = {
  use: [[require("@factorial/stack-javascript"), { outputFormat: "esm" }]],
};

Changing plugin configuration

If you want to change the configuration of any of the used rollup plugins, you can do that like this:

// .factorialrc.js

module.exports = {
  use: [
    [
      require("@factorial/stack-javascript"),
      {
        plugins: {
          "@rollup/plugin-commonjs": { … }
        }
      }
    ]
  ],
};

Adding a rollup plugin

Changing plugin configuration

If you want to add an additional rollup plugin, you can do that like this:

// .factorialrc.js

const myPlugin = require("myRollupPlugin");

module.exports = {
  use: [
    [
      require("@factorial/stack-javascript"),
      {
        plugins: {
          "myRollupPlugin": { … }
        }
      }
    ]
  ],
};

Make sure you added it to your devDependencies in the package.json.

Extending or overwriting linting rules

If you need to extend or overwrite the linting rules, you can do that like this:

// .eslintrc.js

module.exports = {
  root: true,
  extends: […],
  rules: {
    ...
  },
};

Exclude files from linting

If you want to exclude files from linting, you can do it by adding a .eslintignore file to your root where you reference all files that should be ignored.

Tests

The test task uses jest, which "by default it looks for .js, .jsx, .ts and .tsx files inside of __tests__ folders, as well as any files with a suffix of .test or .spec (e.g. Component.test.js or Component.spec.js). It will also find files called test.js or spec.js." (Jest documentation)

Extending the jest config

If you need to extend the jest config, you can do that like this:

const jestConfig = require("@factorial/stack-javascript").jest;
const deepMerge = require("deepmerge");

module.exports = deepMerge(jestConfig, {
  ...
});