feat: publish to NPM instead of JSR

The package is published to NPM now, instead of JSR.

The TypeScript sources are compiled to JavaScript using `@swc/core` and the
type declarations are emitted using TypeScript 7. Both steps run from the
`prepublishOnly` hook into the `npm/` folder, which is what `exports` points
to. This mirrors the setup used in `nRFCloud/billing-service-proto`.

`semantic-release` publishes via `@semantic-release/npm` instead of
`@sebbo2002/semantic-release-jsr`.

Author: coderbyheart

.github/workflows/test-and-release.yaml

@@ -4,7 +4,6 @@ on: push
 
 env:
   GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-  JSR_TOKEN: ${{ secrets.JSR_TOKEN }}
 
 permissions:
   contents: write
@@ -22,14 +21,16 @@ jobs:
         with:
           node-version: ">=24.18.1 <25"
           cache: "npm"
+          registry-url: "https://registry.npmjs.org"
 
       - name: Install dependencies
         run: npm ci --no-audit
 
+      - name: Compile TypeScript
+        run: npx tsc
+
       - name: Test
         run: npm test
 
       - name: Semantic release
-        run: |
-          npm install -D @sebbo2002/semantic-release-jsr
-          npx semantic-release
+        run: npx semantic-release

.gitignore

@@ -1 +1,2 @@
 node_modules/
+npm/

.npm/compile.ts

@@ -0,0 +1,50 @@
+/*
+ * Compile source for NPM
+ */
+
+import swc from '@swc/core'
+import { mkdirSync, rmSync, writeFileSync } from 'node:fs'
+import { glob } from 'node:fs/promises'
+import path, { dirname } from 'node:path'
+import { fileURLToPath } from 'node:url'
+import tsconfig from './tsconfig.npm.json' with { type: 'json' }
+import { updateImports } from './updateImports.ts'
+
+const __dirname = dirname(fileURLToPath(import.meta.url))
+
+const outDir = path.join(__dirname, '..', 'npm')
+
+try {
+	rmSync(outDir, { recursive: true, force: true })
+} catch {
+	// pass
+}
+
+for await (const file of glob(
+	tsconfig.include.map((include) => path.join('.npm', include)),
+)) {
+	if (file.endsWith('.spec.ts') || file.endsWith('.test.ts')) continue
+	let compiled = (
+		await swc.transformFile(file, {
+			jsc: {
+				parser: {
+					syntax: 'typescript',
+				},
+				target: 'es2024',
+			},
+			module: {
+				type: 'es6',
+			},
+		})
+	).code
+
+	compiled = updateImports(compiled)
+
+	const targetFile = path.join(outDir, file.replace(/\.ts$/, '.js'))
+
+	mkdirSync(dirname(targetFile), { recursive: true })
+
+	writeFileSync(targetFile, compiled, 'utf8')
+
+	console.log(file)
+}

.npm/tsconfig.npm.json

@@ -0,0 +1,11 @@
+{
+  "extends": "../tsconfig.json",
+  "compilerOptions": {
+    "emitDeclarationOnly": true,
+    "declaration": true,
+    "noEmit": false,
+    "rootDir": ".."
+  },
+  "include": ["../*.ts"],
+  "exclude": ["../*.spec.ts", "../*.test.ts"]
+}

.npm/updateImports.spec.ts

@@ -0,0 +1,11 @@
+import assert from 'node:assert'
+import { describe, it } from 'node:test'
+import { updateImports } from './updateImports.ts'
+
+void describe('updateImports', () => {
+	void it('replaces .ts with .js in relative imports', () => {
+		const input = `import { foo } from './bar.ts';`
+		const expected = `import { foo } from './bar.js';`
+		assert.equal(updateImports(input), expected)
+	})
+})

.npm/updateImports.ts

@@ -0,0 +1,2 @@
+export const updateImports = (source: string): string =>
+	source.replace(/from ['"](.+?)\.ts['"]/g, "from '$1.js'")

CONTRIBUTING.md

@@ -1,9 +1,9 @@
 # Contributing to `@nrfcloud/wait-for-it`
 
 This is a published library
-([`@nrfcloud/wait-for-it`](https://jsr.io/@nrfcloud/wait-for-it) on JSR). The
-sections below cover the development setup, how to test your changes, and how a
-new version gets released.
+([`@nrfcloud/wait-for-it`](https://www.npmjs.com/package/@nrfcloud/wait-for-it)
+on NPM). The sections below cover the development setup, how to test your
+changes, and how a new version gets released.
 
 ## Development setup
 
@@ -16,8 +16,9 @@ new version gets released.
 
 ## Testing
 
-Run `npm test` for the unit tests. They run on Node.js' built-in test runner
-(`node --test`) directly against the TypeScript sources.
+1. Run `npx tsc` to type-check the project.
+1. Run `npm test` for the unit tests. They run on Node.js' built-in test runner
+   (`node --test`) directly against the TypeScript sources.
 
 ## Squash your commits
 
@@ -29,12 +30,25 @@ Run `npm test` for the unit tests. They run on Node.js' built-in test runner
 1. Get the code reviewed.
 1. Once approved and CI passes, rebase or squash away!
 
+## Building the NPM package
+
+The package is published as compiled JavaScript with type declarations in the
+`npm/` folder, which is created by the `prepublishOnly` hook:
+
+1. [`.npm/compile.ts`](.npm/compile.ts) transpiles the TypeScript sources using
+   [`@swc/core`](https://www.npmjs.com/package/@swc/core) and rewrites the `.ts`
+   import specifiers to `.js`.
+1. [TypeScript 7](https://www.npmjs.com/package/typescript) emits the type
+   declarations, using [`.npm/tsconfig.npm.json`](.npm/tsconfig.npm.json).
+
+Run `npm run prepublishOnly` to build it locally.
+
 ## Releasing a new version
 
 1. [`semantic-release` in the Test&Release workflow](.github/workflows/test-and-release.yaml)
    takes care of determining the next version from the conventional commits,
    creating a new GitHub release and publishing the package to
-   [JSR](https://jsr.io/@nrfcloud/wait-for-it).
+   [NPM](https://www.npmjs.com/package/@nrfcloud/wait-for-it).
 
 Once a new version is published, consumers can bump the dependency to pick it
 up.

README.md

@@ -1,11 +1,11 @@
 # `@nrfcloud/wait-for-it`
 
-<https://jsr.io/@nrfcloud/wait-for-it>
+<https://www.npmjs.com/package/@nrfcloud/wait-for-it>
 
 ## Install with NPM
 
 ```bash
-npx jsr add (--save-prod|--save-dev) @nrfcloud/wait-for-it
+npm i (--save-prod|--save-dev) @nrfcloud/wait-for-it
 ```
 
 ## Usage