oidc-caep-client 0.2.7-next.1 → 0.2.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +1 -1
  2. package/docs/spa-guide.md +1 -1
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -30,7 +30,7 @@ That adds it to the `dependencies` in your `package.json`:
30
30
 
31
31
  **Versions** are ordinary semver: `0.2.0`, `0.2.1`, … `^0.2.0` takes every later 0.2 release and nothing from 0.3, which may change the API. For a reproducible build, pin one version (`"oidc-caep-client": "0.2.1"`) and let your lock file record it.
32
32
 
33
- **Release channels.** `latest` (the default) is built from `main`. `next` is built from `develop`, ahead of a release, as pre-releases such as `0.2.1-next.3`: `npm install oidc-caep-client@next`. A range like `^0.2.0` never resolves to a pre-release.
33
+ **Release channels.** `latest` (the default) is built from `main`. `next` holds pre-releases such as `0.2.1-next.3`, published by hand from `main` when one is needed: `npm install oidc-caep-client@next`. A range like `^0.2.0` never resolves to a pre-release.
34
34
 
35
35
  **TypeScript.** The package ships type declarations (`types/*.d.ts`, generated from the source's JSDoc), so TypeScript finds them through `package.json` with nothing to install or configure. The library itself stays JavaScript, and works the same from both:
36
36
 
package/docs/spa-guide.md CHANGED
@@ -100,7 +100,7 @@ Two settings look similar but **don't** grant a scope:
100
100
  npm install oidc-caep-client
101
101
  ```
102
102
 
103
- That adds `"oidc-caep-client": "^0.2.0"` to the `dependencies` in your `package.json`, and installs its one dependency, [`jose`](https://github.com/panva/jose). Versions are ordinary semver, so `^0.2.0` takes every later 0.2 release; pin one version instead for reproducible builds. `npm install oidc-caep-client@next` gets the latest pre-release built from `develop`, ahead of a release. The README's [Installing](../README.md#installing) section has the details.
103
+ That adds `"oidc-caep-client": "^0.2.0"` to the `dependencies` in your `package.json`, and installs its one dependency, [`jose`](https://github.com/panva/jose). Versions are ordinary semver, so `^0.2.0` takes every later 0.2 release; pin one version instead for reproducible builds. `npm install oidc-caep-client@next` gets the latest pre-release, when there is one newer than `latest`. The README's [Installing](../README.md#installing) section has the details.
104
104
 
105
105
  **TypeScript.** The package ships its own declarations, so a TypeScript app imports it the same way and gets the types, e.g. `type SecurityEvent` for an event handler's parameter. Set `"module": "NodeNext"` or your bundler's resolution so TypeScript reads the package's `exports`. The examples below are JavaScript; they compile as TypeScript unchanged.
106
106
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "oidc-caep-client",
3
- "version": "0.2.7-next.1",
3
+ "version": "0.2.8",
4
4
  "description": "In-browser OpenID Connect public client (PKCE, PAR, DPoP, RFC 9207) with token caching/auto-refresh and a Shared Signals (SSF) / CAEP event receiver",
5
5
  "homepage": "https://rcbj.github.io/oidc-caep-client/",
6
6
  "repository": {