2018-02-16 22:32:24 +00:00
|
|
|
{
|
2018-05-05 07:04:42 +00:00
|
|
|
"name": "sourcecred",
|
2019-08-07 18:12:11 +00:00
|
|
|
"version": "0.4.0",
|
2019-08-13 15:46:23 +00:00
|
|
|
"private": false,
|
2018-02-16 22:32:24 +00:00
|
|
|
"dependencies": {
|
2020-03-07 23:37:42 +00:00
|
|
|
"aphrodite": "^2.4.0",
|
2019-07-19 12:01:36 +00:00
|
|
|
"base64url": "^3.0.1",
|
2020-03-07 23:37:42 +00:00
|
|
|
"better-sqlite3": "^6.0.1",
|
2019-08-23 15:51:35 +00:00
|
|
|
"bottleneck": "^2.19.5",
|
2020-03-07 23:43:59 +00:00
|
|
|
"chalk": "^3.0.0",
|
2020-03-07 23:37:42 +00:00
|
|
|
"commonmark": "^0.29.1",
|
|
|
|
|
"d3-array": "^2.4.0",
|
|
|
|
|
"d3-format": "^1.4.3",
|
|
|
|
|
"d3-scale": "^3.2.1",
|
|
|
|
|
"d3-scale-chromatic": "^1.5.0",
|
|
|
|
|
"d3-time": "^1.1.0",
|
|
|
|
|
"d3-time-format": "^2.2.3",
|
2019-07-21 15:05:21 +00:00
|
|
|
"deep-freeze": "^0.0.1",
|
2020-03-07 23:37:42 +00:00
|
|
|
"express": "^4.17.1",
|
|
|
|
|
"fs-extra": "^8.1.0",
|
2020-02-08 23:46:23 +00:00
|
|
|
"globby": "^11.0.0",
|
2020-03-07 23:37:42 +00:00
|
|
|
"history": "^3.3.0",
|
|
|
|
|
"htmlparser2": "^4.1.0",
|
2018-07-27 19:38:40 +00:00
|
|
|
"isomorphic-fetch": "^2.2.1",
|
|
|
|
|
"json-stable-stringify": "^1.0.1",
|
|
|
|
|
"lodash.clonedeep": "^4.5.0",
|
|
|
|
|
"lodash.isequal": "^4.5.0",
|
|
|
|
|
"lodash.sortby": "^4.7.0",
|
2020-03-07 23:37:42 +00:00
|
|
|
"object-assign": "^4.1.1",
|
|
|
|
|
"pako": "^1.0.11",
|
|
|
|
|
"promise": "^8.1.0",
|
|
|
|
|
"react": "^16.13.0",
|
|
|
|
|
"react-dom": "^16.13.0",
|
|
|
|
|
"react-icons": "^3.9.0",
|
|
|
|
|
"react-markdown": "^4.3.1",
|
|
|
|
|
"react-router": "^3.2.6",
|
|
|
|
|
"recharts": "^1.8.5",
|
Initial Timeline Explorer
This commit adds a TimelineExplorer for visualizing timeline cred data.
The centerpiece is the TimelineCredChart, a d3-based line chart showing
how the top users' cred evolved over time. It has features like tooltips,
reasonable ticks on the x axis, a legend, and filtering out line
segments that stay on the x axis.
An inspection test is included, which you can check out here:
http://localhost:8080/test/TimelineCredView/
Also, you can run it for any loaded repository at:
http://localhost:8080/timeline/$repoOwner/$repoName
This commit also includes new dependencies:
- recharts (for the charts)
- react-markdown (for rendering the Markdown descriptions)
- remove-markdown (so the legend will be clean text)
- d3-time-format for date axis generation
- d3-scale and d3-scale-chromatic for color scales
Test plan: The frontend code is mostly untested, in keeping with my
observation that the costs of testing the old explorer were really high,
and the tests brought little benefit. However, I have manually tested it
thoroughly. Also, there is an inspection test for the TimelineCredView
(see above).
2019-05-31 17:17:27 +00:00
|
|
|
"remove-markdown": "^0.3.0",
|
2018-08-22 18:37:29 +00:00
|
|
|
"retry": "^0.12.0",
|
2020-03-07 23:37:42 +00:00
|
|
|
"rimraf": "^3.0.2",
|
2019-05-20 14:12:57 +00:00
|
|
|
"svg-react-loader": "^0.4.6",
|
2020-03-07 23:43:59 +00:00
|
|
|
"tmp": "0.0.33",
|
2020-03-07 23:37:42 +00:00
|
|
|
"whatwg-fetch": "^2.0.4"
|
2018-07-27 19:38:40 +00:00
|
|
|
},
|
|
|
|
|
"devDependencies": {
|
2020-03-07 23:37:42 +00:00
|
|
|
"@babel/core": "^7.8.7",
|
|
|
|
|
"@babel/plugin-proposal-class-properties": "^7.8.3",
|
Add the grain/grain.js (#1696)
This commit adds a `grain/grain.js` module, which contains a type and
logic for representing Grain balances with 18 digits of precision. We
use the native BigInt type (and add the necessary babel plugin to
support it).
Unfortunately, Flow does not yet support BigInts (see
[facebook/flow#6639]). To hack around this, we lie to Flow, claiming
that BigInts are numbers, and we expect/suppress the flow errors
whenever we actually instantiate one. For example:
```js
// $ExpectFlowError
const myBigInt = 5n;
```
We can use the BigInt operators like `+`, `-`, `>` without flow errors,
since these actually exist on numbers too. However, flow will fail to
detect improper combinations of regular numbers and BigInts:
```js
// $ExpectFlowError
const x = 5n;
const y = x + 5;
// Uncaught TypeError: Cannot mix BigInt and other types
```
Since any improper mixing will result in a runtime error, these issues
will be easy to detect via unit tests.
In addition to adding the basic Grain type, I exported a `format`
function which will display Grain balances in a human readable way.
It supports arbitrary decimal precision, groups large amounts with comma
separators, handles negative numbers, and adds a suffix string.
The format method is thoroughly documented and tested. Thanks to @Beanow
for valuable feedback on its implementation.
Test plan: See included unit tests. `yarn test` passes.
[facebook/flow#6639]: https://github.com/facebook/flow/issues/6639
2020-03-14 19:31:02 +00:00
|
|
|
"@babel/plugin-syntax-bigint": "^7.8.3",
|
2020-03-07 23:37:42 +00:00
|
|
|
"@babel/preset-env": "^7.8.7",
|
|
|
|
|
"@babel/preset-flow": "^7.8.3",
|
|
|
|
|
"@babel/preset-react": "^7.8.3",
|
|
|
|
|
"babel-eslint": "^10.1.0",
|
2020-03-07 23:43:59 +00:00
|
|
|
"babel-jest": "^25.1.0",
|
2019-07-11 04:15:53 +00:00
|
|
|
"babel-loader": "^8.0.6",
|
2020-03-07 23:37:42 +00:00
|
|
|
"copy-webpack-plugin": "^5.1.1",
|
|
|
|
|
"css-loader": "^3.4.2",
|
|
|
|
|
"dotenv": "^8.2.0",
|
|
|
|
|
"dotenv-expand": "^5.1.0",
|
|
|
|
|
"enzyme": "^3.11.0",
|
|
|
|
|
"enzyme-adapter-react-16": "^1.15.2",
|
|
|
|
|
"enzyme-to-json": "^3.4.4",
|
|
|
|
|
"eslint": "^6.8.0",
|
|
|
|
|
"eslint-plugin-flowtype": "^4.6.0",
|
|
|
|
|
"eslint-plugin-import": "^2.20.1",
|
|
|
|
|
"eslint-plugin-jsx-a11y": "^6.2.3",
|
2019-10-04 15:22:12 +00:00
|
|
|
"eslint-plugin-react": "7.16.0",
|
2020-04-15 04:58:05 +00:00
|
|
|
"file-loader": "^6.0.0",
|
2020-03-06 17:46:10 +00:00
|
|
|
"flow-bin": "^0.120.1",
|
2020-03-07 23:43:59 +00:00
|
|
|
"jest": "^25.1.0",
|
2020-03-07 23:37:42 +00:00
|
|
|
"jest-fetch-mock": "^3.0.2",
|
2020-03-22 05:26:42 +00:00
|
|
|
"prettier": "^2.0.1",
|
2020-03-07 23:37:42 +00:00
|
|
|
"raf": "^3.4.1",
|
|
|
|
|
"react-dev-utils": "^5.0.3",
|
|
|
|
|
"static-site-generator-webpack-plugin": "^3.4.2",
|
2020-04-15 04:57:57 +00:00
|
|
|
"url-loader": "^4.0.0",
|
2020-03-07 23:37:42 +00:00
|
|
|
"webpack": "^4.42.0",
|
|
|
|
|
"webpack-cli": "^3.3.11",
|
|
|
|
|
"webpack-dev-server": "^3.10.3",
|
|
|
|
|
"webpack-manifest-plugin": "^2.2.0",
|
2018-07-27 19:38:40 +00:00
|
|
|
"webpack-node-externals": "^1.7.2"
|
2018-02-16 22:32:24 +00:00
|
|
|
},
|
2019-07-05 19:10:02 +00:00
|
|
|
"greenkeeper": {
|
|
|
|
|
"ignore": [
|
|
|
|
|
"history",
|
|
|
|
|
"react-dev-utils",
|
|
|
|
|
"react-router",
|
2019-07-18 13:02:52 +00:00
|
|
|
"whatwg-fetch",
|
|
|
|
|
"tmp"
|
2019-07-05 19:10:02 +00:00
|
|
|
]
|
|
|
|
|
},
|
2018-02-16 22:32:24 +00:00
|
|
|
"scripts": {
|
2018-02-18 09:59:28 +00:00
|
|
|
"prettify": "prettier --write '**/*.js'",
|
2020-03-22 05:27:55 +00:00
|
|
|
"check-pretty": "prettier --list-different '**/*.js'",
|
2018-09-05 04:45:10 +00:00
|
|
|
"start": "NODE_ENV=development webpack-dev-server --config config/webpack.config.web.js",
|
|
|
|
|
"build": "NODE_ENV=production webpack --config config/webpack.config.web.js",
|
2018-09-05 19:28:27 +00:00
|
|
|
"backend": "NODE_ENV=development webpack --config config/webpack.config.backend.js",
|
2020-01-10 05:27:37 +00:00
|
|
|
"api": "webpack --config config/webpack.config.api.js",
|
2018-07-31 17:53:10 +00:00
|
|
|
"test": "node ./config/test.js",
|
|
|
|
|
"unit": "BABEL_ENV=test NODE_ENV=test jest --env=jsdom",
|
Add `sharness` for shell-based testing (#597)
Summary:
We will shortly want to perform testing of shell scripts; it makes the
most sense to do so via the shell. We could roll our own testing
framework, but it makes more sense to use an existing one. By choosing
Sharness, we’re in good company: `go-ipfs` and `go-multihash` use it as
well, and it’s derived from Git’s testing library. I like it a lot.
For now, we need a dummy test file; our test runner will fail if there
are no tests to run. As soon as we have a real test, we can remove this.
This commit was generated by following the “per-project installation”
instructions at https://github.com/chriscool/sharness, and by
additionally including that repository’s `COPYING` file as
`SHARNESS_LICENSE`, with a header prepended. I considered instead adding
Sharness as a submodule, which is supported and has clear advantages
(e.g., you can update the thing), but opted to avoid the complexity of
submodules for now.
Test Plan:
Create the following tests in the `sharness` directory:
```shell
$ cat sharness/good.t
#!/bin/sh
test_description='demo of passing tests'
. ./sharness.sh
test_expect_success "look at me go" true
test_expect_success EXPENSIVE "this may take a while" 'sleep 2'
test_done
# vim: ft=sh
$ cat sharness/bad.t
#!/bin/sh
test_description='demo of failing tests'
. ./sharness.sh
test_expect_success "I don't feel so good" false
test_done
# vim: ft=sh
```
Note that `yarn sharness` and `yarn test` fail appropriately. Note that
`yarn sharness-full` fails appropriately after taking two extra seconds,
and `yarn test --full` runs the latter. Each failure message should
print the name of the failing test case, not just the suite name, and
should indicate that the passing tests passed.
Then, remove `sharness/bad.t`, and note that the above commands all
pass, with the `--full` variants still taking longer.
Finally, remove `sharness/good.t`, and note that the above commands all
pass (and all pass quickly).
wchargin-branch: add-sharness
2018-08-06 19:56:25 +00:00
|
|
|
"sharness": "make -sC ./sharness prove PROVE_OPTS=-f TEST_OPTS='--chain-lint'",
|
2018-10-31 18:06:48 +00:00
|
|
|
"sharness-full": "make -sC ./sharness prove PROVE_OPTS=-vf TEST_OPTS='-v --chain-lint --long'",
|
2019-01-07 22:38:21 +00:00
|
|
|
"coverage": "yarn run unit --coverage",
|
2018-03-02 22:39:54 +00:00
|
|
|
"flow": "flow",
|
2018-07-31 17:53:10 +00:00
|
|
|
"lint": "eslint src config --max-warnings 0"
|
2018-02-17 21:28:47 +00:00
|
|
|
},
|
2019-08-13 15:46:23 +00:00
|
|
|
"license": "(MIT OR Apache-2.0)",
|
2018-02-17 21:28:47 +00:00
|
|
|
"jest": {
|
|
|
|
|
"collectCoverageFrom": [
|
|
|
|
|
"src/**/*.{js,jsx,mjs}"
|
|
|
|
|
],
|
|
|
|
|
"setupFiles": [
|
2018-07-26 22:08:14 +00:00
|
|
|
"<rootDir>/config/polyfills.js",
|
|
|
|
|
"<rootDir>/config/jest/setupJest.js"
|
2018-02-17 21:28:47 +00:00
|
|
|
],
|
|
|
|
|
"testMatch": [
|
|
|
|
|
"<rootDir>/src/**/__tests__/**/*.{js,jsx,mjs}",
|
|
|
|
|
"<rootDir>/src/**/?(*.)(spec|test).{js,jsx,mjs}"
|
|
|
|
|
],
|
|
|
|
|
"testEnvironment": "node",
|
|
|
|
|
"testURL": "http://localhost",
|
|
|
|
|
"transform": {
|
|
|
|
|
"^.+\\.(js|jsx|mjs)$": "<rootDir>/node_modules/babel-jest",
|
|
|
|
|
"^.+\\.css$": "<rootDir>/config/jest/cssTransform.js",
|
|
|
|
|
"^(?!.*\\.(js|jsx|mjs|css|json)$)": "<rootDir>/config/jest/fileTransform.js"
|
|
|
|
|
},
|
|
|
|
|
"transformIgnorePatterns": [
|
|
|
|
|
"[/\\\\]node_modules[/\\\\].+\\.(js|jsx|mjs)$"
|
|
|
|
|
],
|
|
|
|
|
"moduleNameMapper": {
|
|
|
|
|
"^react-native$": "react-native-web"
|
|
|
|
|
},
|
|
|
|
|
"moduleFileExtensions": [
|
|
|
|
|
"web.js",
|
|
|
|
|
"js",
|
|
|
|
|
"json",
|
|
|
|
|
"web.jsx",
|
|
|
|
|
"jsx",
|
2019-07-14 19:05:49 +00:00
|
|
|
"node",
|
|
|
|
|
"mjs"
|
2018-02-17 21:28:47 +00:00
|
|
|
]
|
|
|
|
|
},
|
2018-07-27 21:32:30 +00:00
|
|
|
"files": [
|
|
|
|
|
"/bin",
|
|
|
|
|
"/build"
|
2018-09-02 23:11:56 +00:00
|
|
|
]
|
2018-02-16 22:32:24 +00:00
|
|
|
}
|
