@babylonjs/inspector 5.0.0-rc.3 → 5.0.0-rc.6

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/package.json CHANGED
@@ -1,47 +1,35 @@
1
1
  {
2
- "author": {
3
- "name": "David CATUHE"
4
- },
5
2
  "name": "@babylonjs/inspector",
6
- "description": "The Babylon.js inspector.",
7
- "version": "5.0.0-rc.3",
8
- "repository": {
9
- "type": "git",
10
- "url": "https://github.com/BabylonJS/Babylon.js.git"
11
- },
12
- "main": "babylon.inspector.bundle.max.js",
3
+ "version": "5.0.0-rc.6",
4
+ "module": "dist/babylon.inspector.bundle.max.js",
5
+ "main": "dist/babylon.inspector.bundle.max.js",
6
+ "typings": "dist/babylon.inspector.module.d.ts",
13
7
  "files": [
14
- "babylon.inspector.bundle.max.js",
15
- "babylon.inspector.bundle.max.js.map",
16
- "babylon.inspector.module.d.ts",
8
+ "dist",
17
9
  "readme.md"
18
10
  ],
19
- "typings": "babylon.inspector.module.d.ts",
20
- "keywords": [
21
- "3D",
22
- "javascript",
23
- "html5",
24
- "webgl",
25
- "babylonjs",
26
- "inspector"
27
- ],
28
- "license": "Apache-2.0",
11
+ "scripts": {
12
+ "build": "npm run clean && npm run build:dev && npm run build:prod && npm run build:declaration",
13
+ "build:dev": "webpack --env development",
14
+ "build:prod": "webpack --env production",
15
+ "build:declaration": "build-tools -c pud --config ./config.json",
16
+ "clean": "rimraf dist"
17
+ },
29
18
  "dependencies": {
30
- "@babylonjs/core": "5.0.0-rc.3",
31
- "@babylonjs/gui": "5.0.0-rc.3",
32
- "@babylonjs/loaders": "5.0.0-rc.3",
33
- "@babylonjs/materials": "5.0.0-rc.3",
34
- "@babylonjs/serializers": "5.0.0-rc.3",
35
- "babylonjs-gltf2interface": "5.0.0-rc.3",
19
+ "@babylonjs/core": "^5.0.0-rc.6",
20
+ "@babylonjs/gui": "^5.0.0-rc.6",
21
+ "react": "^17.0.2",
22
+ "react-dom": "^17.0.2",
36
23
  "tslib": "^2.3.1"
37
24
  },
38
25
  "peerDependencies": {
39
26
  "@types/react": ">=16.7.3",
40
27
  "@types/react-dom": ">=16.0.9"
41
28
  },
42
- "engines": {
43
- "node": "*"
29
+ "devDependencies": {
30
+ "@lts/gui": "1.0.0",
31
+ "rimraf": "^3.0.2",
32
+ "typescript": "^4.4.4"
44
33
  },
45
- "module": "babylon.inspector.bundle.max.js",
46
- "esnext": "babylon.inspector.bundle.max.js"
47
- }
34
+ "sideEffects": true
35
+ }
package/readme.md CHANGED
@@ -13,7 +13,7 @@ npm install --save-dev @babylonjs/core @babylonjs/inspector
13
13
 
14
14
  # How to use
15
15
 
16
- Afterwards it can be imported to the your project using:
16
+ Afterwards it can be imported to your project using:
17
17
 
18
18
  ```
19
19
  import "@babylonjs/core/Debug/debugLayer";
@@ -22,6 +22,6 @@ import "@babylonjs/inspector";
22
22
 
23
23
  The first line will ensure you can access the property debugLayer of the scene while the second will ensure the inspector can be used within your scene.
24
24
 
25
- This is a great example where code splitting or conditional loading could be use to ensure you are not delivering the inspector if not part of your final app.
25
+ This is a great example where code splitting or conditional loading could be used to ensure you are not delivering the inspector if not part of your final app.
26
26
 
27
- For more information you can have a look at our [our ES6 dedicated documentation](https://doc.babylonjs.com/features/es6_support).
27
+ For more information you can have a look at our [ES6 dedicated documentation](https://doc.babylonjs.com/features/es6_support).