Setting up Unit Tests with TypeScript is sometimes less than intuitive. My aim here is to present the pros and cons of using Typescript and to detail how simple it is to set up typescript unit tests with Jest and Mocha.
If you're trying to install a scoped, internal or private library and you run into authentication or not found errors, please continue reading:
Follow the GitHub docs on installing packages from GPR. To install private or internal packages in a GitHub workflow, you'll need to add a GitHub Action Secret to the repository. Organizations that publish packages from multiple repos should provide an organization-level access token and share that token among repos that need to install other internal or private packages within the organization. Organization secrets can be shared with specific repos by an organization admin.
To configure NPM to instal
- use Go for all backend logic
- use the standard library first (net/http, html/template, context, database/sql)
- use HTMX for interactivity and progressive enhancement (server-rendered HTML first)
- use Pico.css for styling; extend via custom CSS/SCSS only when needed
- keep handlers small and focused (one responsibility per handler)
- return HTML fragments for HTMX requests and full pages for normal requests
- default to small components/templates
The following files have unresolved merge conflicts. Please open each file, find the conflict markers (<<<<<<< / ======= / >>>>>>>), and resolve every conflict by editing the files directly.
Choose resolutions that best preserve the intent of both changes, or combine them if appropriate.
Files with conflicts:
| #!/usr/bin/env bash | |
| set -euo pipefail | |
| usage() { | |
| cat <<'EOF' | |
| Usage: | |
| scripts/mirror-multiarch-image.sh [source-image] [destination-image] | |
| Defaults: | |
| source-image docker.io/library/golang:1.26 |