@flopay/js 1.10.3 → 1.10.5
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 +11 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -14,6 +14,17 @@ pnpm add @flopay/js
|
|
|
14
14
|
|
|
15
15
|
For React applications, `@flopay/react` builds on this package and renders the complete checkout.
|
|
16
16
|
|
|
17
|
+
### Choosing and upgrading a release
|
|
18
|
+
|
|
19
|
+
Read the [SDK changelog](https://changelog.sdk.flopay.com) for the target release's changes and
|
|
20
|
+
integration guidance before upgrading. When installing more than one `@flopay/*` package directly,
|
|
21
|
+
choose the same released version for each and commit the resulting lockfile. You do not need to
|
|
22
|
+
install packages that are already supplied as dependencies.
|
|
23
|
+
|
|
24
|
+
Confirm that the chosen version is available on npm for every package you are updating. A merged
|
|
25
|
+
GitHub pull request alone does not mean publication has finished. If that exact version is not yet
|
|
26
|
+
available, wait for publication rather than mixing versions or installing a repository branch.
|
|
27
|
+
|
|
17
28
|
## Usage
|
|
18
29
|
|
|
19
30
|
### Initialize the SDK
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@flopay/js",
|
|
3
|
-
"version": "1.10.
|
|
3
|
+
"version": "1.10.5",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"sideEffects": false,
|
|
6
6
|
"publishConfig": {
|
|
@@ -32,7 +32,7 @@
|
|
|
32
32
|
],
|
|
33
33
|
"dependencies": {
|
|
34
34
|
"@stripe/stripe-js": "^9.8.0",
|
|
35
|
-
"@flopay/shared": "1.10.
|
|
35
|
+
"@flopay/shared": "1.10.5"
|
|
36
36
|
},
|
|
37
37
|
"devDependencies": {
|
|
38
38
|
"jsdom": "^29.1.1",
|