status-im
/
sourcecred
mirror of https://github.com/status-im/sourcecred.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
sourcecred/package.json

146 lines
4.2 KiB
JSON
Raw Normal View History

Frontend setup (#13) * Initial infrastructure for sourcecred-explorer. Setup npm, yarn, flow, jest using scaffolding from create-react-app. - used create-react-app to get the basic pieces - added support for flow via instructions in the create-react-app user guide - added flow-typed so that flow+jest will work well * Add some additional resources * Add index.css * Remove .DS_STORE per @wchargin's suggestion
2018-02-16 22:32:24 +00:00
{
Change package.json name to sourcecred (#215)
2018-05-05 07:04:42 +00:00
"name": "sourcecred",
Release version 0.4.0 (#1271) Test plan: `yarn test --full`
2019-08-07 18:12:11 +00:00
"version": "0.4.0",
Make SourceCred a public package (#1284) I'm mostly motivated by wanting to get greenkeeper lockfile auto-updating working (see #1269) although this is also a first step towards making SourceCred usable from NPM (#1232). For now, see this as us making sure we claim the sourcecred package name on npm (see: https://www.npmjs.com/package/sourcecred). I also fixed the license spec so that it's valid SPDX.
2019-08-13 15:46:23 +00:00
"private": false,
Frontend setup (#13) * Initial infrastructure for sourcecred-explorer. Setup npm, yarn, flow, jest using scaffolding from create-react-app. - used create-react-app to get the basic pieces - added support for flow via instructions in the create-react-app user guide - added flow-typed so that flow+jest will work well * Add some additional resources * Add index.css * Remove .DS_STORE per @wchargin's suggestion
2018-02-16 22:32:24 +00:00
"dependencies": {
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
2020-03-07 23:37:42 +00:00
"aphrodite": "^2.4.0",
Use url encoding and make _getProjectIds async Test plan: `yarn test --full` still passes. Also, I've ensured that the async `_getProjectIds` is still usable in our webpack configs (via modifying and testing the dependent commits).
2019-07-19 12:01:36 +00:00
"base64url": "^3.0.1",
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
2020-03-07 23:37:42 +00:00
"better-sqlite3": "^6.0.1",
discourse fetch: add rate limiting (#1321) This implements rate limiting to the Discourse fetch logic, so that we can actually load nontrivial servers without getting a 529 failure. We could have used retry; I thought it was more polite to actually limit the rate at which we make requests. However, to avoid seeing 529s in practice, I left a bit of a buffer: we make only 55 requests per minute, although 60 would be allowed. If we want to improve Discourse loading time, we could boost up to the full 60 request/min, but add in retries. (Or we could switch to retries entirely.) Test plan: This logic is untested, however my full discourse-plugin branch uses it to do full Discourse loads without issue.
2019-08-23 15:51:35 +00:00
"bottleneck": "^2.19.5",
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
2020-03-07 23:37:42 +00:00
"chalk": "^2.4.2",
"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",
Replace `Object.freeze` with `deepFreeze` Throughout the codebase, we freeze objects when we want to ensure that their properties are never altered -- e.g. because they are a plugin declaration, or are being re-used for various test cases. We generally use `Object.freeze`. This has the disadvantage that it does not work recursively, so a frozen object's mutable fields and properties can still be mutated. (E.g. if `const obj = Object.freeze({foo: []})`, then `obj.foo.push(1)` will succeed in mutating the 'frozen' object). Sometimes we anticipate this and explicitly freeze the sub-fields (which is tedious); sometimes we forget (which invites errors). This change simply replaces all instances of Object.freeze with [deep-freeze], so we don't need to worry about the issue at all anymore. Test plan: `yarn test` passes (after updating snapshots); `git grep Object.freeze` returns no hits. [deep-freeze]: https://www.npmjs.com/package/deep-freeze
2019-07-21 15:05:21 +00:00
"deep-freeze": "^0.0.1",
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
2020-03-07 23:37:42 +00:00
"express": "^4.17.1",
"fs-extra": "^8.1.0",
Initiatives: validate and read files from local directory (#1644) Helper functions intended to be used in succession by `loadDirectory`. Only `_validatePath` provides helfpul error messages. It's the caller's responsiblity to do this first. Introduces dependency `globby` for globbing with a Promises API.
2020-02-08 23:46:23 +00:00
"globby": "^11.0.0",
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
2020-03-07 23:37:42 +00:00
"history": "^3.3.0",
"htmlparser2": "^4.1.0",
Reorganize dependencies and devDependencies (#540) This commit is a good faith effort to separate our dependencies (code that SourceCred app or CLI require to run) from devDependencies (all other deps) in our package.json. We don't have any actual dependents, so it's hard to test this distinction. Hence, it's a good faith effort. Test plan: `rm -r node_modules && yarn && yarn travis` works.
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",
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
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",
Retry GitHub queries with exponential backoff (#699) Summary: This patch adds independent exponential backoff to each individual GitHub GraphQL query. We remove the fixed `GITHUB_DELAY_MS` delay before each query in favor of this solution, which requires no additional configuration (thus resolving a TODO in the process). We use the NPM module `retry` with its default settings: namely, a maximum of 10 retries with factor-2 backoff starting at 1000ms. Empirically, it seems very unlikely that we should require much more than 2 retries for a query. (See Test Plan for more details.) This is both a short-term unblocker and a good kind of thing to have in the long term. Test Plan: Note that `yarn test --full` passes, including `fetchGithubRepoTest.sh`. Consider manual testing as follows. Add `console.info` statements in `retryGithubFetch`, then load a large repository like TensorFlow, and observe the output: ```shell $ node bin/sourcecred.js load --plugin github tensorflow/tensorflow 2>&1 | ts -s '%.s' 0.252566 Fetching repo... 0.258422 Trying... 5.203014 Trying... [snip] 1244.521197 Trying... 1254.848044 Will retry (n=1)... 1260.893334 Trying... 1271.547368 Trying... 1282.094735 Will retry (n=1)... 1283.349192 Will retry (n=2)... 1289.188728 Trying... [snip] 1741.026869 Ensuring no more pages... 1742.139978 Creating view... 1752.023697 Stringifying... 1754.697116 Writing... 1754.697772 Done. ``` This took just under half an hour, with 264 queries total, of which: - 225 queries required 0 retries; - 38 queries required exactly 1 retry; - 1 query required exactly 2 retries; and - 0 queries required 3 or more retries. wchargin-branch: github-backoff
2018-08-22 18:37:29 +00:00
"retry": "^0.12.0",
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
2020-03-07 23:37:42 +00:00
"rimraf": "^3.0.2",
Add a FileUploader component, with inspection test (#1149) * Add FileUploader with inspection test TODO: get it working * Add a FileUploader component, with inspection test This adds a FileUploader component, which allows the user to upload JSON files. Rather than using automated testing, it has an inspection test. The inspection test may be run by navigating to: http://localhost:8080/test/FileUploader/ This commit also adds some basic utility functions for defining inspection tests to `routeData.js`. We should improve support for inspection tests in the future; see [#1148]. [#1148]: https://github.com/sourcecred/sourcecred/issues/1148 Test plan: Ran the included inspection test.
2019-05-20 14:12:57 +00:00
"svg-react-loader": "^0.4.6",
try reverting tmp upgrade (#1202) After merging #1201, we started seeing build failures ([1], [2]) on CircleCI. I can't reproduce them locally, but they seem related to the `tmp` module, so let's try reverting the upgrade. Test plan: `yarn test` passes locally. Let's see how it does on CI. [1]: https://circleci.com/gh/sourcecred/sourcecred/1091 [2]: https://circleci.com/gh/sourcecred/sourcecred/1092
2019-07-05 23:22:04 +00:00
"tmp": "^0.0.33",
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
2020-03-07 23:37:42 +00:00
"whatwg-fetch": "^2.0.4"
Reorganize dependencies and devDependencies (#540) This commit is a good faith effort to separate our dependencies (code that SourceCred app or CLI require to run) from devDependencies (all other deps) in our package.json. We don't have any actual dependents, so it's hard to test this distinction. Hence, it's a good faith effort. Test plan: `rm -r node_modules && yarn && yarn travis` works.
2018-07-27 19:38:40 +00:00
},
"devDependencies": {
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
2020-03-07 23:37:42 +00:00
"@babel/core": "^7.8.7",
"@babel/plugin-proposal-class-properties": "^7.8.3",
"@babel/preset-env": "^7.8.7",
"@babel/preset-flow": "^7.8.3",
"@babel/preset-react": "^7.8.3",
"babel-eslint": "^10.1.0",
"babel-jest": "^24.9.0",
Upgrade babel to 7 I moved `config/babel.js` to `.babelrc.js` because it seemed like babel 7 really wanted that. I also blew away our (complicated, copied from create-react-app) config and replaced it with a much, much simpler one. Test plan: `yarn test` passes, `yarn start` still serves a working server, and `scripts/build_static_site.sh` still produces a working site. Possibly we lost some nice features re: React debugging; if so I'll add them back as I miss them.
2019-07-11 04:15:53 +00:00
"babel-loader": "^8.0.6",
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
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",
Update eslint-plugin-react to the latest version 🚀 (#1400) * chore(package): update eslint-plugin-react to version 7.16.0 * chore(package): update lockfile yarn.lock
2019-10-04 15:22:12 +00:00
"eslint-plugin-react": "7.16.0",
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
2020-03-07 23:37:42 +00:00
"file-loader": "^5.1.0",
chore(package): update flow-bin to version 0.120.1 (#1691) Closes #1690 Co-authored-by: greenkeeper[bot] <23040076+greenkeeper[bot]@users.noreply.github.com>
2020-03-06 17:46:10 +00:00
"flow-bin": "^0.120.1",
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
2020-03-07 23:37:42 +00:00
"jest": "^24.9.0",
"jest-fetch-mock": "^3.0.2",
"prettier": "^1.19.1",
"raf": "^3.4.1",
"react-dev-utils": "^5.0.3",
"static-site-generator-webpack-plugin": "^3.4.2",
Update url-loader to the latest version 🚀 (#1470) * chore(package): update url-loader to version 3.0.0 * chore(package): update lockfile yarn.lock
2019-12-09 13:57:52 +00:00
"url-loader": "^3.0.0",
Chore: make all minor-version package upgrades (#1692) Preparing for release #1679 Note: due to a regression, not upgrading eslint-plugin-react See https://github.com/yannickcr/eslint-plugin-react/issues/2570 Also updated package.json to latest semver in-range versions. Note, this changes all packages (other than eslint-plugin-react) to ^x.x.x format.
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",
Reorganize dependencies and devDependencies (#540) This commit is a good faith effort to separate our dependencies (code that SourceCred app or CLI require to run) from devDependencies (all other deps) in our package.json. We don't have any actual dependents, so it's hard to test this distinction. Hence, it's a good faith effort. Test plan: `rm -r node_modules && yarn && yarn travis` works.
2018-07-27 19:38:40 +00:00
"webpack-node-externals": "^1.7.2"
Frontend setup (#13) * Initial infrastructure for sourcecred-explorer. Setup npm, yarn, flow, jest using scaffolding from create-react-app. - used create-react-app to get the basic pieces - added support for flow via instructions in the create-react-app user guide - added flow-typed so that flow+jest will work well * Add some additional resources * Add index.css * Remove .DS_STORE per @wchargin's suggestion
2018-02-16 22:32:24 +00:00
},
Update dependencies to enable Greenkeeper 🌴 (#1201) This commit enables Greenkeeper, along with an initial upgrade push for our dependencies. I've reverted a number of upgrades, and also added them to the greenkeeper ignore list. They mostly relate to babel/webpack stuff, which I'm reluctant to dive into now (there have been major upgrades for both babel and webpack) but we should address eventually. There are also a few oddballs like whatwg-fetch and history. Test plan: `yarn test --full` passes.
2019-07-05 19:10:02 +00:00
"greenkeeper": {
"ignore": [
"history",
"react-dev-utils",
"react-router",
Update dependencies to enable Greenkeeper 🌴 (#1231) * chore(package): update dependencies * revert tmp upgrade I'm having test failures when `tmp` is upgraded; they seem to repro only when many tests are running at once. Since we have no issues with the older version of tmp, let's just keep an old tmp and inform Greenkeeper not to touch it. Test plan: `yarn test`
2019-07-18 13:02:52 +00:00
"whatwg-fetch",
"tmp"
Update dependencies to enable Greenkeeper 🌴 (#1201) This commit enables Greenkeeper, along with an initial upgrade push for our dependencies. I've reverted a number of upgrades, and also added them to the greenkeeper ignore list. They mostly relate to babel/webpack stuff, which I'm reluctant to dive into now (there have been major upgrades for both babel and webpack) but we should address eventually. There are also a few oddballs like whatwg-fetch and history. Test plan: `yarn test --full` passes.
2019-07-05 19:10:02 +00:00
]
},
Frontend setup (#13) * Initial infrastructure for sourcecred-explorer. Setup npm, yarn, flow, jest using scaffolding from create-react-app. - used create-react-app to get the basic pieces - added support for flow via instructions in the create-react-app user guide - added flow-typed so that flow+jest will work well * Add some additional resources * Add index.css * Remove .DS_STORE per @wchargin's suggestion
2018-02-16 22:32:24 +00:00
"scripts": {
Set up prettier as an autoformatter (#18) Setup prettier precommit, with yarn prettify to reformat. - Prettier runs as a precommit hook and fails if code is improperly formatted. - Run `yarn prettify` to reformat the project.
2018-02-18 09:59:28 +00:00
"prettify": "prettier --write '**/*.js'",
Setup travis CI testing (#58) Observe that it passed on this commit, but failed builds [#2: Break Tests][2], [#3: Break Flow][3], and [#4: Break Prettier][4]. Close #23 [2]: https://travis-ci.org/sourcecred/sourcecred/builds/348453195 [3]: https://travis-ci.org/sourcecred/sourcecred/builds/348454983 [4]: https://travis-ci.org/sourcecred/sourcecred/builds/348455387
2018-03-02 22:39:54 +00:00
"check-pretty": "prettier --list-different '**/*.js'",
Rename `makeWebpackConfig` to `webpack.config.web` (#770) Summary: The distinction was useful while `makeWebpackConfig` was being developed (between #562 and #570), but is now confusing: we have a web config and a backend config, and it is clearer if we name them as such. Test Plan: All of `yarn start`, `yarn build`, and `yarn test --full` work. wchargin-branch: webpack-config-web
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",
backend: invoke Webpack directly in package script (#782) Summary: This commit removes the `config/backend.js` script and replaces it with a direct invocation of Webpack. This enables us to use command-line arguments to Webpack, like `--output-path`. Test Plan: Note that `rm -rf bin; yarn backend` still works, and that the resulting applications work (`node bin/sourcecred.js load`). Note that `yarn test` and `yarn test --full` still work. wchargin-branch: backend-webpack-direct
2018-09-05 19:28:27 +00:00
"backend": "NODE_ENV=development webpack --config config/webpack.config.backend.js",
api: extract browser-friendly build target (#1536) Summary: This re-packages the build for the internal APIs exposed under #1526 to be more browser-friendly. Removing `target: "node"` (and adding an explicit `globalObject: "this"` for best-effort cross-compatibility) is the biggest change from the backend build; removing all the extra loaders and static site generation is the biggest change from the frontend build. This build configuration is forked from `webpack.config.backend.js`. Test Plan: Run `yarn api`, then upload the contents of `dist/api.js` to an Observable notebook and require it as an ES module. Verify that the SourceCred APIs are exposed: e.g., `sourcecred.core.graph.Graph` should be a valid constructor. wchargin-branch: api-build
2020-01-10 05:27:37 +00:00
"api": "webpack --config config/webpack.config.api.js",
package.json: reorganize test commands (#571) Summary: Running `yarn test` (equiv. `npm test` or `npm run test`) now runs all checks. It takes the place of the former `yarn travis`. This is more in line with the expectation of a top-level `test` command: if it passes, your code is good. The `unit` command now runs Jest once, not in watch mode. It takes the place of the former `ci-test`. To run tests in watch mode, run any of the following: - `yarn unit --watch`, or - `npm run unit -- --watch`, or - `npm unit -- --watch`. This behavior is more consistent with the standard behavior of commands like `make test`. It is also empirically what @wchargin and @decentralion want most of the time. Test Plan: Verify that each of the scripts `test`, `unit`, and `coverage` passes. Verify that each of the aforementioned `--watch` invocations works. Verify that `.travis.yml` has the correct `script:` command. wchargin-branch: reorganize-test-command
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'",
test: run Sharness verbosely on nightly jobs (#958) Summary: Tests that run only on nightly builds (`yarn test --full`) and fail only on CI (not locally) are a bit more inconvenient to debug when they fail. This patch makes the `yarn test --full` script print all the intermediate output in Sharness tests, which can be helpful. We don’t do this for `yarn test` simply because it generates a ton of spam even on successful tests. Test Plan: $ yarn test --full 2>&1 | wc -l 1173 wchargin-branch: test-full-verbose
2018-10-31 18:06:48 +00:00
"sharness-full": "make -sC ./sharness prove PROVE_OPTS=-vf TEST_OPTS='-v --chain-lint --long'",
Tests use yarn not npm (#1038) Currently, our underlying test script uses npm rather than yarn to execute the tests. This is awkward, because we use yarn everywhere else in lieu of npm. It turns out that some setups have node available without npm, and in such environments our tests fail with a cryptic ENOENT error. This changes the tests to use yarn instead. Test plan: `yarn test --full` passes. Thanks to @wpank for help uncovering this issue.
2019-01-07 22:38:21 +00:00
"coverage": "yarn run unit --coverage",
Setup travis CI testing (#58) Observe that it passed on this commit, but failed builds [#2: Break Tests][2], [#3: Break Flow][3], and [#4: Break Prettier][4]. Close #23 [2]: https://travis-ci.org/sourcecred/sourcecred/builds/348453195 [3]: https://travis-ci.org/sourcecred/sourcecred/builds/348454983 [4]: https://travis-ci.org/sourcecred/sourcecred/builds/348455387
2018-03-02 22:39:54 +00:00
"flow": "flow",
package.json: reorganize test commands (#571) Summary: Running `yarn test` (equiv. `npm test` or `npm run test`) now runs all checks. It takes the place of the former `yarn travis`. This is more in line with the expectation of a top-level `test` command: if it passes, your code is good. The `unit` command now runs Jest once, not in watch mode. It takes the place of the former `ci-test`. To run tests in watch mode, run any of the following: - `yarn unit --watch`, or - `npm run unit -- --watch`, or - `npm unit -- --watch`. This behavior is more consistent with the standard behavior of commands like `make test`. It is also empirically what @wchargin and @decentralion want most of the time. Test Plan: Verify that each of the scripts `test`, `unit`, and `coverage` passes. Verify that each of the aforementioned `--watch` invocations works. Verify that `.travis.yml` has the correct `script:` command. wchargin-branch: reorganize-test-command
2018-07-31 17:53:10 +00:00
"lint": "eslint src config --max-warnings 0"
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
},
Make SourceCred a public package (#1284) I'm mostly motivated by wanting to get greenkeeper lockfile auto-updating working (see #1269) although this is also a first step towards making SourceCred usable from NPM (#1232). For now, see this as us making sure we claim the sourcecred package name on npm (see: https://www.npmjs.com/package/sourcecred). I also fixed the license spec so that it's valid SPDX.
2019-08-13 15:46:23 +00:00
"license": "(MIT OR Apache-2.0)",
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"jest": {
"collectCoverageFrom": [
"src/**/*.{js,jsx,mjs}"
],
"setupFiles": [
Add jest-fetch-mock as dev dependency (#528) Also add config/jest/setupJest.js so we can configure jest-fetch-mock Test plan: I have verified that mocked fetch works as expected in a downstream commit.
2018-07-26 22:08:14 +00:00
"<rootDir>/config/polyfills.js",
"<rootDir>/config/jest/setupJest.js"
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
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",
tweak: jest loads .mjs last This resolves an issue that caused jest tests to fail when depending on a module that ships .mjs files (encountered via a transitive dep of react-markdown). See https://github.com/facebook/create-react-app/pull/4085 for context. Test plan: I have a future commit which tests a file that depends on react-markdown. The tests fail to run before this commit, and they run without issue afterwards.
2019-07-14 19:05:49 +00:00
"node",
"mjs"
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
]
},
Upgrade oclif packages to latest (#542) This required adding a [files property] to the package.json, otherwise oclif started complaining. Test plan: I manually tested both CLI commands, and they seem fine. [files property]: https://docs.npmjs.com/files/package.json#files
2018-07-27 21:32:30 +00:00
"files": [
"/bin",
"/build"
Replace `oclif` with `cli` (#744) Summary: This commit changes the CLI to use the code in `cli` instead of `oclif`. A subsequent commit will remove the dependency on OClif altogether. Resolves #580. Test Plan: Note that `yarn backend; node bin/sourcecred.js help` works. Note that the documentation in the README is still correct. wchargin-branch: cli-replace-oclif
2018-09-02 23:11:56 +00:00
]
Frontend setup (#13) * Initial infrastructure for sourcecred-explorer. Setup npm, yarn, flow, jest using scaffolding from create-react-app. - used create-react-app to get the basic pieces - added support for flow via instructions in the create-react-app user guide - added flow-typed so that flow+jest will work well * Add some additional resources * Add index.css * Remove .DS_STORE per @wchargin's suggestion
2018-02-16 22:32:24 +00:00
}