mbs-sso-js 0.1.0 → 0.1.1
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.
- package/README.md +2 -20
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,10 +4,10 @@ Launch MBS SSO from HTML, React or React Native while keeping OAuth credentials
|
|
|
4
4
|
|
|
5
5
|
## Install
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Install the versioned release from the npm registry once npm finishes processing it:
|
|
8
8
|
|
|
9
9
|
```sh
|
|
10
|
-
npm install
|
|
10
|
+
npm install mbs-sso-js@0.1.1
|
|
11
11
|
```
|
|
12
12
|
|
|
13
13
|
For local development, run `pnpm sdk:build` in the SSO repository, then install its `public/sdk/mbs-sso-js-0.1.0.tgz` file. Node helpers require Node 20+. React and React Native are optional peers; install them only for the adapter you use.
|
|
@@ -53,21 +53,3 @@ The Express example uses a development memory session store and refuses producti
|
|
|
53
53
|
The browser adapters know only your start URL. MBS backend improvements remain available in the hosted journey without an SDK update. Changes to the public authorization/token contract may require a new server helper release. Pin the SDK version and test against your registered client. Endpoint behavior is covered by contract tests; a full live sign-in still requires provisioned MBS credentials and NINAuth configuration.
|
|
54
54
|
|
|
55
55
|
Native browser launch and return-link configuration require device validation; this release has not been tested in an iOS/Android emulator.
|
|
56
|
-
|
|
57
|
-
## Publish to the npm registry
|
|
58
|
-
|
|
59
|
-
Run from the SSO repository root:
|
|
60
|
-
|
|
61
|
-
```sh
|
|
62
|
-
pnpm sdk:build
|
|
63
|
-
cd packages/mbs-sso-js
|
|
64
|
-
npm login
|
|
65
|
-
npm publish --dry-run
|
|
66
|
-
npm publish --access public
|
|
67
|
-
```
|
|
68
|
-
|
|
69
|
-
Complete npm's browser login and publishing verification using your own account. The prepublishOnly hook rebuilds the SDK and runs the repository checks and tests. The files allowlist publishes dist, examples and the README. Review the dry-run file list before publishing.
|
|
70
|
-
|
|
71
|
-
The unscoped name `mbs-sso-js` must be available or owned by your npm account. If it is not, change the package name to `@YOUR_NPM_SCOPE/mbs-sso-js` and update the example imports and installation instructions accordingly before release. Confirm your organization's ownership and intended license before publishing; this repository does not choose a license for you.
|
|
72
|
-
|
|
73
|
-
After successful publication, consumers can install `npm install mbs-sso-js` (or the scoped name you chose). Update the hosted documentation and release metadata only after verifying the registry release. For subsequent releases, increment the SDK package version, update the pinned SDK guide/download references, rebuild and publish; npm does not allow overwriting a published name/version pair.
|