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

presetter-preset-esm

v5.0.0

Published

A collection of opinionated preset configurations for typescript projects

Downloads

63

Readme

Logo

🏄🏻 A collection of opinionated configurations for a typescript project for presetter

•   Quick Start   •   Project Structure   •   Customization   •   Scripts   •

npm build maintainability coverage security dependencies license

Features

presetter-preset-esm is a collection of essential dev tools you usually need to setup a typescript project in a fraction of time you usually take via presetter. In addition to a set of opinionated configuration files, it also provides a number of essential lifecycle and helper commands.

  • 🚿 ESLint
  • 🧪 Vitest
  • 💅 Prettier
  • 📤 Standard Version
  • 💯 Typescript

Quick Start

FULL DOCUMENTATION IS AVAILABLE HERE

  1. Bootstrap your project with presetter-preset-esm
npx presetter use presetter-preset-esm

That's. One command and you're set.

  1. Develop and run life cycle scripts provided by the preset

At this point, all development packages specified in the preset are installed, and now you can try to run some example life cycle scripts (e.g. run prepare).

Demo

Project Structure

After installation, your project file structure should resemble the following or with more configuration files if you also installed other presets such as presetter-preset-rollup.

Implement your business logic under source and prepare tests under spec.

TIPS You can always change the source directory to other (e.g. src) by setting the source variable in .presetterrc.json. See the customization section below for more details.

(root)
 ├─ .eslintrc.json
 ├─ .git
 ├─ .husky
 ├─ .npmignore
 ├─ .prettierrc.json
 ├─ .presetterrc.json
 ├─ node_modules
 ├─ source
 │   ├─ <folders>
 │   ├─ index.ts
 │   ├─ (auxiliary).ts
 ├─ spec
 │   ├─ *.spec.ts
 ├─ package.json
 ├─ tsconfig.json
 ├─ tsconfig.build.json
 └─ vitest.config.json

Customization

By default, this preset exports a handy configuration for rollup for a typescript project. But you can further customize (either extending or replacing) the configuration by specifying the change in the config file (.presetterrc or .presetterrc.json).

These settings are available in the config field in the config file. For directories, the setting is specified in the variable field.

The structure of .presetterrc should follow the interface below:

interface PresetterRC {
  /** name of the preset e.g. presetter-preset-esm */
  name: string | string[];
  /** additional configuration passed to the preset for generating the configuration files */
  config?: {
    //  ┌─ configuration for other tools via other presets (e.g. presetter-preset-rollup)
    // ...

    /** configuration to be merged with .eslintrc */
    eslint?: Record<string, unknown>;
    /** configuration to be merged with .lintstagedrc */
    lintstaged?: Record<string, unknown>;
    /** patterns to be added to .gitignore */
    gitignore?: string[];
    /** patterns to be added to .npmignore */
    npmignore?: string[];
    /** configuration to be merged with .presetterrc */
    prettier?: Record<string, unknown>;
    /** configuration to be merged with tsconfig.json */
    tsconfig?: Record<string, unknown>;
    /** a list of config files not to be created */
    ignores?: string[];
  };
  /** relative path to root directories for different file types */
  variable?: {
    /** the directory containing the whole repository (default: .) */
    root?: string;
    /** the directory containing all generated code (default: generated) */
    generated?: string;
    /** the directory containing all source code (default: source) */
    source?: string;
    /** the directory containing all typing files (default: types) */
    types?: string;
    /** the directory containing all output tile (default: source) */
    output?: string;
    /** the directory containing all test files (default: spec) */
    test?: string;
  };
}

Script Template Summary

  • run build: Transpile source code from typescript and replace any mapped paths
  • run clean: Clean up any previously transpiled code
  • run develop -- <file path>: Create a service that run the specified file whenever the source has changed
  • run test: Run all tests
  • run watch: Rerun all tests whenever the source has change
  • run coverage: Run all test with coverage report
  • run release: Bump the version and automatically generate a change log
  • run release -- --prerelease <tag>: Release with a prerelease tag

Notes

  • Since git 2.32 (released on 2020-06-06), git no longer follows .gitignore as a symlink. Therefore, the packaged .gitignore will no longer symlinked but created on the root directory of the project instead.