jlfwong/speedscope
1
1
Fork 0
mirror of https://github.com/jlfwong/speedscope.git synced 2024-11-26 15:45:50 +03:00
Code Issues Projects Releases Wiki Activity
3f79e0fe96
speedscope/package.json

79 lines
1.9 KiB
JSON
Raw Normal View History

Import from stackprof to convenient in-memory format
2017-11-22 11:00:31 +03:00
{
"name": "speedscope",
1.5.3
2020-01-16 11:09:07 +03:00
"version": "1.5.3",
Import from stackprof to convenient in-memory format
2017-11-22 11:00:31 +03:00
"description": "",
Upgrade to TypeScript 3.0.1 (#110) Fixes #103
2018-08-01 11:23:21 +03:00
"repository": "jlfwong/speedscope",
Import from stackprof to convenient in-memory format
2017-11-22 11:00:31 +03:00
"main": "index.js",
Upgrade parcel-bundler to 1.9.2
2018-07-01 01:44:46 +03:00
"bin": {
Reorganize directory structure (#104) While it was kind of nice having everything at the top level, the number of files is now getting a bit unwieldy and hard to understand, so I took a stab at organizing the directories without introducing too much nesting. Test Plan: - Ran `npm run serve` to ensure that local builds still work - Ran `npm run prepack` then `open dist/release/index.html` to ensure that release builds still work - Ran `scripts/deploy.sh` to ensure that the deployed version of the site will still work when I eventually redeploy - Ran `npm run jest` to ensure that tests still work correctly
2018-08-01 10:41:45 +03:00
"speedscope": "./bin/cli.js"
Upgrade parcel-bundler to 1.9.2
2018-07-01 01:44:46 +03:00
},
Import from stackprof to convenient in-memory format
2017-11-22 11:00:31 +03:00
"scripts": {
Reorganize directory structure (#104) While it was kind of nice having everything at the top level, the number of files is now getting a bit unwieldy and hard to understand, so I took a stab at organizing the directories without introducing too much nesting. Test Plan: - Ran `npm run serve` to ensure that local builds still work - Ran `npm run prepack` then `open dist/release/index.html` to ensure that release builds still work - Ran `scripts/deploy.sh` to ensure that the deployed version of the site will still work when I eventually redeploy - Ran `npm run jest` to ensure that tests still work correctly
2018-08-01 10:41:45 +03:00
"deploy": "./scripts/deploy.sh",
"prepack": "./scripts/build-release.sh",
"prettier": "prettier --write 'src/**/*.ts' 'src/**/*.tsx'",
"lint": "eslint 'src/**/*.ts' 'src/**/*.tsx'",
Add support for importing linux "perf script" output (#135) Fixes #119
2018-08-16 20:24:12 +03:00
"jest": "./scripts/test-setup.sh && jest --runInBand",
Add test coverage reporting (#55) This adds an integration with https://coveralls.io/ to report on code coverage of tests
2018-05-30 05:59:04 +03:00
"coverage": "npm run jest -- --coverage && coveralls < coverage/lcov.info",
"test": "tsc --noEmit && npm run lint && npm run coverage",
Reorganize directory structure (#104) While it was kind of nice having everything at the top level, the number of files is now getting a bit unwieldy and hard to understand, so I took a stab at organizing the directories without introducing too much nesting. Test Plan: - Ran `npm run serve` to ensure that local builds still work - Ran `npm run prepack` then `open dist/release/index.html` to ensure that release builds still work - Ran `scripts/deploy.sh` to ensure that the deployed version of the site will still work when I eventually redeploy - Ran `npm run jest` to ensure that tests still work correctly
2018-08-01 10:41:45 +03:00
"serve": "parcel assets/index.html --open --no-autoinstall"
Import from stackprof to convenient in-memory format
2017-11-22 11:00:31 +03:00
},
1.5.2
2019-10-11 04:26:54 +03:00
"files": [
"bin/cli.js",
"dist/release/**",
"!*.map"
],
"browserslist": [
"last 2 Chrome versions",
"last 2 Firefox versions"
],
Import from stackprof to convenient in-memory format
2017-11-22 11:00:31 +03:00
"author": "",
"license": "MIT",
"devDependencies": {
Specify file format for speedscope (#83) This defines a JSON-based file format for speedscope. The motivation for is primarily two things: 1. To enable others to write tools to output profiles which can be read by speedscope 2. To enable others to write tools to handle the output of speedscope, leveraging the variety of importers that speedscope supports Fixes #65
2018-07-08 04:37:28 +03:00
"@types/jest": "22.2.3",
"@types/jszip": "3.1.4",
"@types/node": "10.1.4",
Integrate jest and add first test file (#51) This sets up the first bit of test infrastructure to write and run unit tests on every PR Related to #14 Fixes #7
2018-05-30 00:34:09 +03:00
"@types/pako": "1.0.0",
Upgrade libraries & change release procedure (#8) Previously, I was doing a hacky release process where I had `index.html` serve contents for `jlfwong.github.io/speedscope`, but used `dev.html` locally. This seems like it broke with the latest parcel release, so I just revamped the release process instead. Now, the `release.sh` script creates a temporary shallow clone of the repository, overwrites its contents with build artifacts, runs a local server to verify it's working, then commits and pushes to the `gh-pages` branches.
2018-04-05 10:15:42 +03:00
"aphrodite": "2.1.0",
Specify file format for speedscope (#83) This defines a JSON-based file format for speedscope. The motivation for is primarily two things: 1. To enable others to write tools to output profiles which can be read by speedscope 2. To enable others to write tools to handle the output of speedscope, leveraging the variety of importers that speedscope supports Fixes #65
2018-07-08 04:37:28 +03:00
"coveralls": "3.0.1",
"eslint": "4.19.1",
"eslint-plugin-prettier": "2.6.0",
Bump dependency versions to unbreak build (#253) I ended up in a horrible peer dependency hell and apparently needed to bump the versions of quicktype, typescript, ts-jest, *and* jest to get out of it. But I think I got out of it! Local builds and deployment builds both seem to work after these changes.
2020-01-16 10:32:14 +03:00
"jest": "24.3.0",
Specify file format for speedscope (#83) This defines a JSON-based file format for speedscope. The motivation for is primarily two things: 1. To enable others to write tools to output profiles which can be read by speedscope 2. To enable others to write tools to handle the output of speedscope, leveraging the variety of importers that speedscope supports Fixes #65
2018-07-08 04:37:28 +03:00
"jsverify": "0.8.3",
"jszip": "3.1.5",
Integrate jest and add first test file (#51) This sets up the first bit of test infrastructure to write and run unit tests on every PR Related to #14 Fixes #7
2018-05-30 00:34:09 +03:00
"pako": "1.0.6",
Upgrade parcel-bundler to 1.9.2
2018-07-01 01:44:46 +03:00
"parcel-bundler": "1.9.2",
Upgrade libraries & change release procedure (#8) Previously, I was doing a hacky release process where I had `index.html` serve contents for `jlfwong.github.io/speedscope`, but used `dev.html` locally. This seems like it broke with the latest parcel release, so I just revamped the release process instead. Now, the `release.sh` script creates a temporary shallow clone of the repository, overwrites its contents with build artifacts, runs a local server to verify it's working, then commits and pushes to the `gh-pages` branches.
2018-04-05 10:15:42 +03:00
"preact": "8.2.7",
Switch to redux for global state management (#100) This should allow state to be more easily retained globally when switching views, and should make implementation of cross-view features like search easier too. It also removes the need for `ReloadableComponent` Fixes #78 Test Plan: This changes a lot of how the app works, and a lot of stuff that isn't currently covered by tests, so here's a rough manual test plan: 1. Loaded up http://localhost:1234/, click to load the example profile 2. Switch between views, see that viewport & selection position is now retained when switching views 3. See that clicking on nodes selects them in Time Order & Left Heavy views 4. See that hitting Cmd+S saves a profile 5. See that dropping a profile in works 6. See that dropping a profile + a symbol map works 7. See that visiting localhost:1234/#profileURL=https://raw.githubusercontent.com/jlfwong/speedscope/master/sample/profiles/speedscope/0.1.2/simple-sampled.speedscope.json works 8. See that hitting "r" to toggle recursion flattening works
2018-08-01 09:53:56 +03:00
"preact-redux": "jlfwong/preact-redux#a56dcc4",
Fix the build for node 13.x, make travis test 10, 12, 13, stable (#263) @JustinBeckwith pointed out in #262 that `npm install` was broken in node 13.x, and @DanielRuf pointed in #254 that test fail for node 11+ because of a change to stability of sorting. This PR seeks to address both of those. The installation issue was fixed by just regenerating `package-lock.json` without needing to bump any of the direct dependency versions. The test failure issue requires manual intervention. To fix the sort stability issue, I updated the tests to use the stable sort values (these were all the correct values, though some of the test values were incorrect). To make the suite still pass for node 10, I added a hack where I override `Array.prototype.sort` with a stable implementation that's *only* used in tests (See comments in code for a justification for why) ## Test Plan Before this PR: `npm install` on node 13.x fails & `npm run jest` results in test failures After this PR: `npm install` on node 13.x passes & `npm run jest` passes for node 10, 12, and 13.
2020-04-20 18:26:59 +03:00
"prettier": "2.0.4",
Add go tool pprof import support (#165) This PR adds support for importing from Google's pprof format, which is a gzipped, protobuf encoded file format (that's incredibly well documented!) The [pprof http library](https://golang.org/pkg/net/http/pprof/) also offers an output of the trace file format, which continues to not be supported in speedscope to date (See #77). This will allow importing of profiles generated by the standard library go profiler for analysis of profiles containing heap allocation information, CPU profile information, and a few other things like coroutine creation information. In order to add support for that a number of dependent bits of functionality were added, which should each provide an easier path for future binary input sources - A protobuf decoding library was included ([protobufjs](https://www.npmjs.com/package/protobufjs)) which includes both a protobuf parser generator based on a .proto file & TypeScript definition generation from the resulting generated JavaScript file - More generic binary file import. Before this PR, all supported sources were plaintext, with the exception of Instruments 10 support, which takes a totally different codepath. Now binary file import should work when files are dropped, opened via file browsing, or opened via invocation of the speedscope CLI. - Transparent gzip decoding of imported files (this means that if you were to gzip compress another JSON file, then importing it should still work fine) Fixes #60. -- This is a [donation motivated](https://github.com/jlfwong/speedscope/issues/60#issuecomment-419660710) PR motivated by donations by @davecheney & @jmoiron to [/dev/color](https://www.devcolor.org/welcome) 🎉
2018-09-26 21:33:34 +03:00
"protobufjs": "6.8.8",
Bump dependency versions to unbreak build (#253) I ended up in a horrible peer dependency hell and apparently needed to bump the versions of quicktype, typescript, ts-jest, *and* jest to get out of it. But I think I got out of it! Local builds and deployment builds both seem to work after these changes.
2020-01-16 10:32:14 +03:00
"quicktype": "15.0.209",
Switch to redux for global state management (#100) This should allow state to be more easily retained globally when switching views, and should make implementation of cross-view features like search easier too. It also removes the need for `ReloadableComponent` Fixes #78 Test Plan: This changes a lot of how the app works, and a lot of stuff that isn't currently covered by tests, so here's a rough manual test plan: 1. Loaded up http://localhost:1234/, click to load the example profile 2. Switch between views, see that viewport & selection position is now retained when switching views 3. See that clicking on nodes selects them in Time Order & Left Heavy views 4. See that hitting Cmd+S saves a profile 5. See that dropping a profile in works 6. See that dropping a profile + a symbol map works 7. See that visiting localhost:1234/#profileURL=https://raw.githubusercontent.com/jlfwong/speedscope/master/sample/profiles/speedscope/0.1.2/simple-sampled.speedscope.json works 8. See that hitting "r" to toggle recursion flattening works
2018-08-01 09:53:56 +03:00
"redux": "^4.0.0",
Bump dependency versions to unbreak build (#253) I ended up in a horrible peer dependency hell and apparently needed to bump the versions of quicktype, typescript, ts-jest, *and* jest to get out of it. But I think I got out of it! Local builds and deployment builds both seem to work after these changes.
2020-01-16 10:32:14 +03:00
"ts-jest": "24.3.0",
"typescript": "3.2.4",
Upgrade to TypeScript 3.0.1 (#110) Fixes #103
2018-08-01 11:23:21 +03:00
"typescript-eslint-parser": "17.0.1",
Revert "Support importing partial JSON files (#202)" This reverts commit cfc8fe8f6e995be00129b7a43101dd6ed16e8c81.
2019-02-09 05:33:30 +03:00
"uglify-es": "3.2.2"
Integrate jest and add first test file (#51) This sets up the first bit of test infrastructure to write and run unit tests on every PR Related to #14 Fixes #7
2018-05-30 00:34:09 +03:00
},
"jest": {
"transform": {
"^.+\\.tsx?$": "ts-jest"
},
Fix the build for node 13.x, make travis test 10, 12, 13, stable (#263) @JustinBeckwith pointed out in #262 that `npm install` was broken in node 13.x, and @DanielRuf pointed in #254 that test fail for node 11+ because of a change to stability of sorting. This PR seeks to address both of those. The installation issue was fixed by just regenerating `package-lock.json` without needing to bump any of the direct dependency versions. The test failure issue requires manual intervention. To fix the sort stability issue, I updated the tests to use the stable sort values (these were all the correct values, though some of the test values were incorrect). To make the suite still pass for node 10, I added a hack where I override `Array.prototype.sort` with a stable implementation that's *only* used in tests (See comments in code for a justification for why) ## Test Plan Before this PR: `npm install` on node 13.x fails & `npm run jest` results in test failures After this PR: `npm install` on node 13.x passes & `npm run jest` passes for node 10, 12, and 13.
2020-04-20 18:26:59 +03:00
"setupFilesAfterEnv": [
"./src/jest-setup.js"
],
Integrate jest and add first test file (#51) This sets up the first bit of test infrastructure to write and run unit tests on every PR Related to #14 Fixes #7
2018-05-30 00:34:09 +03:00
"testRegex": "\\.test\\.tsx?$",
1.5.2
2019-10-11 04:26:54 +03:00
"collectCoverageFrom": [
"**/*.{ts,tsx}",
"!**/*.d.{ts,tsx}"
],
"moduleFileExtensions": [
"ts",
"tsx",
"js",
"jsx",
"json"
]
Add a CLI to load the target file in your default browser (#88) This PR add a CLI speedscope which load file given as an argument in your default browser. Expected usage looks like: ``` speedscope /path/to/profile ``` Note that since we're using base64 encoded strings as a transport for this, this won't work with multi-file profiles, like the Instruments .trace files. This could be augmented to support that by archiving the contents, but that can be handled in a different PR. This PR also set up a viable model for integrating speedscope into other projects. By replicating the contents of `cli.js` in other languages, integration should be possible in other languages with no dependency upon node in any way. Distribution should consist of just HTML, JS, and CSS assets to be loaded in browser. Test Plan: - Ran the following to simulate a publish & subsequent installation: ``` $ npm pack $ mv speedscope-0.1.0.tgz /tmp/ $ cd /tmp $ tar -xvvf speedscope-0.1.0.tgz $ cd package $ npm install --only=production $ ./cli.js Opening file:///private/tmp/package/dist/release/index.html in your default browser $ ./cli.js ~/code/speedscope/sample/profiles/Chrome/65/timeline.json Creating temp file /var/folders/l0/qtd9z14973s2tw81vmzwkyp00000gp/T/speedscope-1531023992823-3880.js Creating temp file /var/folders/l0/qtd9z14973s2tw81vmzwkyp00000gp/T/speedscope-1531023992823-3880.html Opening file:///var/folders/l0/qtd9z14973s2tw81vmzwkyp00000gp/T/speedscope-1531023992823-3880.html in your default browser ``` Fixes #24
2018-07-08 07:33:02 +03:00
},
"dependencies": {
"opn": "5.3.0"
Import from stackprof to convenient in-memory format
2017-11-22 11:00:31 +03:00
}
Fix the build for node 13.x, make travis test 10, 12, 13, stable (#263) @JustinBeckwith pointed out in #262 that `npm install` was broken in node 13.x, and @DanielRuf pointed in #254 that test fail for node 11+ because of a change to stability of sorting. This PR seeks to address both of those. The installation issue was fixed by just regenerating `package-lock.json` without needing to bump any of the direct dependency versions. The test failure issue requires manual intervention. To fix the sort stability issue, I updated the tests to use the stable sort values (these were all the correct values, though some of the test values were incorrect). To make the suite still pass for node 10, I added a hack where I override `Array.prototype.sort` with a stable implementation that's *only* used in tests (See comments in code for a justification for why) ## Test Plan Before this PR: `npm install` on node 13.x fails & `npm run jest` results in test failures After this PR: `npm install` on node 13.x passes & `npm run jest` passes for node 10, 12, and 13.
2020-04-20 18:26:59 +03:00
}
Reference in New Issue Copy Permalink