No description
  • TypeScript 84.4%
  • JavaScript 15.6%
Find a file
2026-05-26 11:24:58 +02:00
scripts chore: Updated files from self. 2026-05-26 11:05:37 +02:00
src chore: Updated files from self. 2026-05-26 11:05:37 +02:00
template chore: Added node: prefix to imports. 2026-05-26 11:01:35 +02:00
tests chore: Updated files from self. 2026-05-26 11:05:37 +02:00
.gitignore version 0.1.10 2026-05-24 14:19:14 +02:00
CHANGELOG.md chore: cleanup versioning and prep for merge 2026-05-26 11:24:14 +02:00
LICENSE added LIC 2026-04-13 11:37:54 +02:00
package.json chore: cleanup versioning and prep for merge 2026-05-26 11:24:14 +02:00
README.md docs: updated quick start section to use @latest and omitting 'clear cache' advice 2026-05-25 18:14:54 +02:00
tsconfig.json 4. Updated files from self. 2026-05-25 12:30:55 +02:00

Introduction

<INTRO TEXT>

Table of Contents

  1. Quick Start
  2. Documentation
  3. DevOps
    1. Change Management
    2. Publish

Quick Start

# placeholder:
    # <NEW_PACKAGE: <NEW_PACKAGE>
    # <TEMPLATE_PACKAGE_NAME: @temir.ra/create-template
    # <TEMPLATE_NAME: @temir.ra/template

mkdir -p <NEW_PACKAGE>
cd <NEW_PACKAGE>

# print the latest version
bun info "@temir.ra/create-template" version

# create/update a package from the template in the current directory
bun create --no-install --no-git "@temir.ra/template@latest" .

# set metadata in package.json

bun install

Documentation

The following sections explain the configurations and conventions baked into the generated package. Useful when adapting it to fit specific needs.

<DOCUMENTATION>

DevOps

bun update
bun install

bun run clean
bun run build
bun run tests

bun run dist/cli.bundle.js -- example/

# see publish section for publish instructions

Change Management

  1. Create a new branch for the change.
  2. Make the changes and commit.
  3. Bump the version in package.json.
  4. Add an entry for the new version in CHANGELOG.md.
  5. Pull request the branch.
  6. Ensure package artifacts are current.
  7. Publish.

Publish

Publish to the public npm registry.

# authenticate
npm login
# publish
bun publish --registry https://registry.npmjs.org/ --access public