v6.0.0 - Deno/JSR first

.github/workflows/ci-test.yml

@@ -1,37 +1,27 @@
-# GitHub actions
-# https://docs.github.com/en/free-pro-team@latest/actions
-
 name: ci-test
 
 on: [push, pull_request]
 
 jobs:
   test:
-
     runs-on: ubuntu-latest
-
     strategy:
       matrix:
-        node_version: [22.x, 24.x, 26.x]
+        deno-version: ["lts", "canary"]
 
     steps:
-    - uses: actions/checkout@v7
+      - uses: actions/checkout@v7
+
+      - name: Setup Deno
+        uses: denoland/setup-deno@v2
+        with:
+          deno-version: ${{ matrix.deno-version }}
 
-    - name: setup Node.js v${{ matrix.node_version }}
-      uses: actions/setup-node@v7
-      with:
-        node-version: ${{ matrix.node_version }}
+      - name: lint
+        run: deno lint
 
-    - name: run npm scripts
-      run: |
-        npm install
-        npm run lint
-        npm run test
+      - name: test
+        run: deno test --allow-all
 
-    - name: cache node modules
-      uses: actions/cache@v6
-      with:
-        path: ~/.npm
-        key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
-        restore-keys: |
-          ${{ runner.os }}-node-
+      - name: audit
+        run: deno audit

.github/workflows/jsr-release.yml

@@ -0,0 +1,32 @@
+name: jsr-release
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      id-token: write
+
+    steps:
+      - uses: actions/checkout@v7
+
+      - name: Setup Deno
+        uses: denoland/setup-deno@v2
+        with:
+          deno-version: lts
+
+      - name: lint
+        run: deno lint
+
+      - name: test
+        run: deno test --allow-all
+
+      - name: audit
+        run: deno audit
+
+      - name: publish to jsr
+        run: deno publish

.gitignore

@@ -3,6 +3,9 @@ logs
 *.log
 *.debug
 
+# Build output
+npm/
+
 # Runtime data
 *.pid
 *.seed

CONTRIBUTING.md

@@ -10,8 +10,7 @@ As an OSS, it's better to follow the Unix philosophy: "do one thing and do it we
 
 Please avoid using libaries other than those available in the standard library, unless necessary.
 
-This library needs to be simple and flexible to run on multiple platforms such as Deno, Bun, or even browser.
-
+This library needs to be simple and flexible to run on multiple platforms (Deno, Node, Bun).
 
 ## Coding convention
 
@@ -22,34 +21,21 @@ Make sure your code lints before opening a pull request.
 cd oembed-extractor
 
 # check coding convention issue
-npm run lint
+deno lint
 
 # auto fix coding convention issue
-npm run lint:fix
+deno lint --fix
 ```
 
-*When you run `npm test`, the linting process will be triggered at first.*
-
-
 ## Testing
 
 Be sure to run the unit test suite before opening a pull request. An example test run is shown below.
 
 ```bash
 cd oembed-extractor
-npm test
+deno test --allow-all
 ```
 
-![oembed-extractor unit test](https://i.imgur.com/Nr5BgUx.png)
-
-If test coverage decreased, please check test scripts and try to improve this number.
-
-
-## Documentation
-
-If you've changed APIs, please update README and [the examples](examples).
-
-
 ## Clean commit histories
 
 When you open a pull request, please ensure the commit history is clean.
@@ -58,12 +44,6 @@ Squash the commits into logical blocks, perhaps a single commit if that makes se
 What you want to avoid is commits such as "WIP" and "fix test" in the history.
 This is so we keep history on master clean and straightforward.
 
-For people new to git, please refer the following guides:
-
-- [Writing good commit messages](https://github.com/erlang/otp/wiki/writing-good-commit-messages)
-- [Commit Message Guidelines](https://gist.github.com/robertpainsi/b632364184e70900af4ab688decf6f53)
-
-
 ## License
 
 By contributing to `@extractus/oembed-extractor`, you agree that your contributions will be licensed under its [MIT license](LICENSE).