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

tacer

v1.0.0

Published

An easier way to create a Javascript project.

Downloads

3

Readme

tacer CircleCI

Create your own template and hide all bundling details.

Intro

'Tacer' means 'to be silent' in Interlingua. What tacer does is making bundling process silent or invisible.

If you've used create-react-app, you must be suprised by its bundling process. You don't need install babel, webpack or rollup mannually. The only thing you should do you run npm start

Now, use tacer to create your own scaffold. All the bundling configures should be written once and used anywhere. Your project folder becomes simple and clear if webpack.config.js, rollup.config.js or jest.config.js are not in the folder.

How To Use

Install globally

npm install -g tacer
tacer react path/to/project
tacer https://github.com/IdanLoo/tacer-template-react path/to/project

Via npx

npx tacer react path/to/project
npx tacer https://github.com/IdanLoo/tacer-template-react path/to/project

Usage

tacer <template> [path]
  • template: required, a package name or a git repository url.

    tacer always assume template is named with prefix tacer-template-, so it tries to download tacer-template-react if a react given.

    There are some out-of-box templates now.

    • react: React + TypeScript + Jest + styled-components
    • koa: Koa + TypeScript + Jest
    • lib: A library template for published to npmjs
    • bin: A binary template
  • path: optional

    default: process.cwd()

    The path of the new project located.

How To Create Template

Althought I have provided some templates, they may not satisfy you. If you'd like to create one, go ahead.

Let's say we are going to create a template for Electron.

Seed

The template of templates is alse a template whick called tacer-template-seed. So you can create like this

tacer seed /path/to/tacer-template-electron

Your will see a folder on the given path.

NOTICE: tacer always assume the package is named with prefix tacer-template-. So if you want to create an Electron template, you need name it as tacer-template-electron.

Template

Create a folder named template in /path/to/tacer-template-electron and put some things (package.json, index.js, .gitignore, etc.) into it. You can just copy an existing project and rename as template.

Handle Bundling

You may notice there is a scripts folder in /path/to/tacer-template-electron. Each script in this folder exports one function which can be called by tacer-script.

Add "start": "tacer-script start" and "build": "tacer-script build" scripts into template/package.json. You can add other commands as you like which provided in the scripts folder.

See more details in above templates.

Validate

How could we know if the template works? Add a devDependency to the template.

npm install --save-dev file:..
// or
yarn add -D file:..

So that you can try npm start, npm build or other commands provided in the tacer-template-electron

Have Fun!