@seriousgaming/sdk 1.0.0-alpha.1 → 1.0.0-alpha.2
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 +4 -0
- package/package.json +7 -1
package/README.md
CHANGED
|
@@ -4,8 +4,12 @@ The library a Serious Gaming game imports: the types and helpers for engines, ho
|
|
|
4
4
|
|
|
5
5
|
You build, test and run a game with the CLI in `@seriousgaming/sdk-tools`. Its documentation starts at `docs/index.md` in that package.
|
|
6
6
|
|
|
7
|
+
The package is ES modules only: import it. Its exports carry no `require` condition, so CommonJS tooling that resolves with `require.resolve` does not find it.
|
|
8
|
+
|
|
7
9
|
## Stability
|
|
8
10
|
|
|
11
|
+
A version with a prerelease suffix, such as `1.0.0-alpha.1`, carries none of these guarantees: it can change in any way before the release it leads to. Until 1.0.0 ships, npm's `latest` tag points at a prerelease, so a bare install gets one.
|
|
12
|
+
|
|
9
13
|
From 1.0.0, these subpaths follow semantic versioning. A breaking change to anything they export waits for a major release:
|
|
10
14
|
|
|
11
15
|
| Subpath | What it holds |
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@seriousgaming/sdk",
|
|
3
|
-
"version": "1.0.0-alpha.
|
|
3
|
+
"version": "1.0.0-alpha.2",
|
|
4
4
|
"description": "SDK for building Serious Gaming games",
|
|
5
5
|
"homepage": "https://sdk.seriousgaming.com/",
|
|
6
6
|
"license": "Apache-2.0",
|
|
@@ -67,6 +67,12 @@
|
|
|
67
67
|
"peerDependenciesMeta": {
|
|
68
68
|
"@testing-library/react": {
|
|
69
69
|
"optional": true
|
|
70
|
+
},
|
|
71
|
+
"react": {
|
|
72
|
+
"optional": true
|
|
73
|
+
},
|
|
74
|
+
"react-dom": {
|
|
75
|
+
"optional": true
|
|
70
76
|
}
|
|
71
77
|
},
|
|
72
78
|
"engines": {
|