memlab 1.1.59 → 2.0.0
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 +3 -3
- package/package.json +11 -11
package/README.md
CHANGED
|
@@ -15,7 +15,7 @@ Features:
|
|
|
15
15
|
API, and memlab will automatically compare JavaScript heap snapshots, filter
|
|
16
16
|
out memory leaks, and aggregate the results
|
|
17
17
|
- **Object-oriented heap traversing API** - Supports the creation of
|
|
18
|
-
self-defined memory leak detector, and enables programmatic analysis JS heap
|
|
18
|
+
self-defined memory leak detector, and enables programmatic analysis of JS heap
|
|
19
19
|
snapshots taken from Chromium-based browsers, Node.js, Electron.js, and Hermes
|
|
20
20
|
- **Memory CLI toolbox** - Built-in toolbox and APIs for finding memory
|
|
21
21
|
optimization opportunities (not necessarily just memory leaks)
|
|
@@ -34,7 +34,7 @@ npm install -g memlab
|
|
|
34
34
|
### Find Memory Leaks
|
|
35
35
|
|
|
36
36
|
To find memory leaks in Google Maps, you can create a
|
|
37
|
-
[scenario file](https://facebook.github.io/memlab/docs/api/interfaces/
|
|
37
|
+
[scenario file](https://facebook.github.io/memlab/docs/api/core/src/interfaces/IScenario) defining how
|
|
38
38
|
to interact with the Google Maps, let's name it `test-google-maps.js`:
|
|
39
39
|
|
|
40
40
|
```javascript
|
|
@@ -112,7 +112,7 @@ memlab view-heap --snapshot <PATH TO .heapsnapshot FILE>
|
|
|
112
112
|
You can optionally specify a specific heap object with the object's id: `--node-id @28173` to pinpoint a specific object.
|
|
113
113
|
|
|
114
114
|
**Self-defined leak detector**: If you want to use a self-defined leak detector, add a `leakFilter` callback
|
|
115
|
-
([doc](https://facebook.github.io/memlab/docs/api/interfaces/
|
|
115
|
+
([doc](https://facebook.github.io/memlab/docs/api/core/src/interfaces/IScenario/#-optional-leakfilter-leakfiltercallback))
|
|
116
116
|
in the scenario file. `filterLeak` will be called for every unreleased heap
|
|
117
117
|
object (`node`) allocated by the target interaction.
|
|
118
118
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "memlab",
|
|
3
|
-
"version": "
|
|
3
|
+
"version": "2.0.0",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"description": "memlab is a framework that analyzes memory and finds memory leaks in JavaScript applications.",
|
|
6
6
|
"author": "Liang Gong <lgong@meta.com>",
|
|
@@ -27,19 +27,19 @@
|
|
|
27
27
|
"snapshot"
|
|
28
28
|
],
|
|
29
29
|
"dependencies": {
|
|
30
|
-
"@memlab/api": "^
|
|
31
|
-
"@memlab/cli": "^
|
|
32
|
-
"@memlab/core": "^
|
|
33
|
-
"@memlab/e2e": "^
|
|
34
|
-
"@memlab/heap-analysis": "^
|
|
35
|
-
"@memlab/lens": "^
|
|
30
|
+
"@memlab/api": "^2.0.0",
|
|
31
|
+
"@memlab/cli": "^2.0.0",
|
|
32
|
+
"@memlab/core": "^2.0.0",
|
|
33
|
+
"@memlab/e2e": "^2.0.0",
|
|
34
|
+
"@memlab/heap-analysis": "^2.0.0",
|
|
35
|
+
"@memlab/lens": "^2.0.0",
|
|
36
36
|
"ansi": "^0.3.1",
|
|
37
37
|
"babar": "^0.2.0",
|
|
38
38
|
"chalk": "^4.0.0",
|
|
39
39
|
"fs-extra": "^4.0.2",
|
|
40
40
|
"minimist": "^1.2.8",
|
|
41
|
-
"puppeteer": "^
|
|
42
|
-
"puppeteer-core": "^
|
|
41
|
+
"puppeteer": "^24.2.0",
|
|
42
|
+
"puppeteer-core": "^24.2.0",
|
|
43
43
|
"string-width": "^4.2.0",
|
|
44
44
|
"util.promisify": "^1.1.1",
|
|
45
45
|
"xvfb": "^0.4.0"
|
|
@@ -48,10 +48,10 @@
|
|
|
48
48
|
"@types/fs-extra": "^9.0.3",
|
|
49
49
|
"@types/jest": "^27.4.1",
|
|
50
50
|
"@types/minimist": "^1.2.5",
|
|
51
|
-
"@types/node": "^
|
|
51
|
+
"@types/node": "^25.0.0",
|
|
52
52
|
"jest": "^29.6.2",
|
|
53
53
|
"ts-jest": "^29.1.1",
|
|
54
|
-
"typescript": "^5.
|
|
54
|
+
"typescript": "^5.9.3"
|
|
55
55
|
},
|
|
56
56
|
"scripts": {
|
|
57
57
|
"preinstall": "node bin/preinstall",
|