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

@tangible/builder

v1.8.4

Published

Tangible Builder: Develop, build, beautify, schema, docs, test, serve

Downloads

58

Readme

Tangible Builder

Develop, build, beautify, schema, docs, test, serve

Requirement

Node.js must be installed, with its package manager, npm.

Install

Add to package.json

{
  "scripts": {
    "dev": "tgb dev",
    "build": "tgb build"
  },
  "devDependencies": {
    "@tangible/builder": "*"
  }
}

Install

npm install

From the project root folder, the builder is available on the command line as npx tgb. Run it to show command descriptions.

Config

Place a file called tangible.config.js in app root folder.

Example

module.exports = {
  build: [
    {
      task: 'js',
      src: 'src/index.js',
      dest: 'build/app.min.js',
      watch: 'src/**/*.js'
    },
    {
      task: 'sass',
      src: 'src/index.scss',
      dest: 'build/app.min.css',
      watch: 'src/**/*.scss'
    },
  ]
}

Build Tasks

The property build is an array of build tasks. Each task has the following schema.

| Property | Description | |---|---| | task | js, sass, or html | | src | Source entry file (can use wildcards for html) | | dest | Destination file (must be folder for html) | | watch | Path of files to watch, in glob syntax | | map | Boolean - Set true to output source map |

React

When building for React in the WordPress admin, add the following property to the js task.

react: 'wp.element'

When using Preact for a compact frontend library, use the alias property.

alias: {
  'react': 'preact/compat',
  'react-dom': 'preact/compat',
}

TypeScript

For building TypeScript, change the watch property of the js task to add file extensions.

watch: 'src/**/*.{js,ts,tsx}'

Server

When using html, you can enable a static file server.

module.exports = {
  build: [
    // ...
  ],
  serve: {
    dir: 'build',
    port: 3000,
    reload: true
  }
}

| Property | Description | |---|---| | dir | Folder to serve from, usually build | | port | Port for the server | | reload | Enable live-reload on file changes (optional) |

The server will run during dev or serve commands.

Use

Make sure to build for production before a new Git commit

Develop

Build during development - watch files and rebuild

npm run dev

After running this command, it will wait and rebuild script and style as you edit the files.

Reload browser to see your changes.

When you're done, press CTRL+C to exit the process.

Build

Build for production - minify script and style

npm run build

Make sure to build for production before publishing.

Lint and Beautify

The lint command ensures code standards, with warnings of any syntax/formatting issues.

npm run lint

The beautify command is similar to lint, but automatically fixes any issues with code standards.

npm run beautify

Commit any changes before running this command, because it can make changes to the code.

Exclude files

With some files, the beautify command has difficulty fixing them.

In that case, pass an option in the script in package.json to exclude the file.

For example, if the builder was installed as Composer module:

  "beautify": "./vendor/tangible/builder/run beautify --ignore=\"includes/file-name\\.php\""

If installed as NPM module:

  "beautify": "tgb beautify --ignore=\"includes/file-name\\.php\""

Note how double quotes and period must be escaped.