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

9013 lines
372 KiB
Plaintext
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
# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
# yarn lockfile v1
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/code-frame@^7.0.0":
version "7.0.0"
resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.0.0.tgz#06e2ab19bdb535385559aabb5ba59729482800f8"
integrity sha512-OfC2uemaknXr87bdLUkWog7nYuliM9Ij5HUcajsVcMCpQrcLmtxRbVFTIqmcSkSeYRBFBRxs2FiUqFJDLdiebA==
dependencies:
"@babel/highlight" "^7.0.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/code-frame@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.5.5.tgz#bc0782f6d69f7b7d49531219699b988f669a8f9d"
integrity sha512-27d4lZoomVyo51VegxI20xZPuSHusqbQag/ztrBC7wegWoQ1nLREPVSKSW8byhTlzTKyNE4ifaTA6lCp7JjpFw==
dependencies:
"@babel/highlight" "^7.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/core@^7.1.0":
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.5.0.tgz#6ed6a2881ad48a732c5433096d96d1b0ee5eb734"
integrity sha512-6Isr4X98pwXqHvtigw71CKgmhL1etZjPs5A67jL/w0TkLM9eqmFR40YrnJvEc1WnMZFsskjsmid8bHZyxKEAnw==
dependencies:
"@babel/code-frame" "^7.0.0"
"@babel/generator" "^7.5.0"
"@babel/helpers" "^7.5.0"
"@babel/parser" "^7.5.0"
"@babel/template" "^7.4.4"
"@babel/traverse" "^7.5.0"
"@babel/types" "^7.5.0"
convert-source-map "^1.1.0"
debug "^4.1.0"
json5 "^2.1.0"
lodash "^4.17.11"
resolve "^1.3.2"
semver "^5.4.1"
source-map "^0.5.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/core@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.5.5.tgz#17b2686ef0d6bc58f963dddd68ab669755582c30"
integrity sha512-i4qoSr2KTtce0DmkuuQBV4AuQgGPUcPXMr9L5MyYAtk06z068lQ10a4O009fe5OB/DfNV+h+qqT7ddNV8UnRjg==
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
dependencies:
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/code-frame" "^7.5.5"
"@babel/generator" "^7.5.5"
"@babel/helpers" "^7.5.5"
"@babel/parser" "^7.5.5"
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/template" "^7.4.4"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/traverse" "^7.5.5"
"@babel/types" "^7.5.5"
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
convert-source-map "^1.1.0"
debug "^4.1.0"
json5 "^2.1.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
lodash "^4.17.13"
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
resolve "^1.3.2"
semver "^5.4.1"
source-map "^0.5.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/generator@^7.4.0", "@babel/generator@^7.5.0":
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/generator/-/generator-7.5.0.tgz#f20e4b7a91750ee8b63656073d843d2a736dca4a"
integrity sha512-1TTVrt7J9rcG5PMjvO7VEG3FrEoEJNHxumRq66GemPmzboLWtIjjcJgk8rokuAS7IiRSpgVSu5Vb9lc99iJkOA==
dependencies:
"@babel/types" "^7.5.0"
jsesc "^2.5.1"
lodash "^4.17.11"
source-map "^0.5.0"
trim-right "^1.0.1"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/generator@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/generator/-/generator-7.5.5.tgz#873a7f936a3c89491b43536d12245b626664e3cf"
integrity sha512-ETI/4vyTSxTzGnU2c49XHv2zhExkv9JHLTwDAFz85kmcwuShvYG2H08FwgIguQf4JC75CBnXAUM5PqeF4fj0nQ==
dependencies:
"@babel/types" "^7.5.5"
jsesc "^2.5.1"
lodash "^4.17.13"
source-map "^0.5.0"
trim-right "^1.0.1"
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/helper-annotate-as-pure@^7.0.0":
version "7.0.0"
resolved "https://registry.yarnpkg.com/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7.0.0.tgz#323d39dd0b50e10c7c06ca7d7638e6864d8c5c32"
integrity sha512-3UYcJUj9kvSLbLbUIfQTqzcy5VX7GRZ/CCDrnOaZorFFM01aXp1+GJwuFGV4NDDoAS+mOUyHcO6UD/RfqOks3Q==
dependencies:
"@babel/types" "^7.0.0"
"@babel/helper-builder-binary-assignment-operator-visitor@^7.1.0":
version "7.1.0"
resolved "https://registry.yarnpkg.com/@babel/helper-builder-binary-assignment-operator-visitor/-/helper-builder-binary-assignment-operator-visitor-7.1.0.tgz#6b69628dfe4087798e0c4ed98e3d4a6b2fbd2f5f"
integrity sha512-qNSR4jrmJ8M1VMM9tibvyRAHXQs2PmaksQF7c1CGJNipfe3D8p+wgNwgso/P2A2r2mdgBWAXljNWR0QRZAMW8w==
dependencies:
"@babel/helper-explode-assignable-expression" "^7.1.0"
"@babel/types" "^7.0.0"
"@babel/helper-builder-react-jsx@^7.3.0":
version "7.3.0"
resolved "https://registry.yarnpkg.com/@babel/helper-builder-react-jsx/-/helper-builder-react-jsx-7.3.0.tgz#a1ac95a5d2b3e88ae5e54846bf462eeb81b318a4"
integrity sha512-MjA9KgwCuPEkQd9ncSXvSyJ5y+j2sICHyrI0M3L+6fnS4wMSNDc1ARXsbTfbb2cXHn17VisSnU/sHFTCxVxSMw==
dependencies:
"@babel/types" "^7.3.0"
esutils "^2.0.0"
"@babel/helper-call-delegate@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/helper-call-delegate/-/helper-call-delegate-7.4.4.tgz#87c1f8ca19ad552a736a7a27b1c1fcf8b1ff1f43"
integrity sha512-l79boDFJ8S1c5hvQvG+rc+wHw6IuH7YldmRKsYtpbawsxURu/paVy57FZMomGK22/JckepaikOkY0MoAmdyOlQ==
dependencies:
"@babel/helper-hoist-variables" "^7.4.4"
"@babel/traverse" "^7.4.4"
"@babel/types" "^7.4.4"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helper-create-class-features-plugin@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/helper-create-class-features-plugin/-/helper-create-class-features-plugin-7.5.5.tgz#401f302c8ddbc0edd36f7c6b2887d8fa1122e5a4"
integrity sha512-ZsxkyYiRA7Bg+ZTRpPvB6AbOFKTFFK4LrvTet8lInm0V468MWCaSYJE+I7v2z2r8KNLtYiV+K5kTCnR7dvyZjg==
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
dependencies:
"@babel/helper-function-name" "^7.1.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helper-member-expression-to-functions" "^7.5.5"
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/helper-optimise-call-expression" "^7.0.0"
"@babel/helper-plugin-utils" "^7.0.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helper-replace-supers" "^7.5.5"
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/helper-split-export-declaration" "^7.4.4"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helper-define-map@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/helper-define-map/-/helper-define-map-7.5.5.tgz#3dec32c2046f37e09b28c93eb0b103fd2a25d369"
integrity sha512-fTfxx7i0B5NJqvUOBBGREnrqbTxRh7zinBANpZXAVDlsZxYdclDp467G1sQ8VZYMnAURY3RpBUAgOYT9GfzHBg==
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
dependencies:
"@babel/helper-function-name" "^7.1.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/types" "^7.5.5"
lodash "^4.17.13"
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/helper-explode-assignable-expression@^7.1.0":
version "7.1.0"
resolved "https://registry.yarnpkg.com/@babel/helper-explode-assignable-expression/-/helper-explode-assignable-expression-7.1.0.tgz#537fa13f6f1674df745b0c00ec8fe4e99681c8f6"
integrity sha512-NRQpfHrJ1msCHtKjbzs9YcMmJZOg6mQMmGRB+hbamEdG5PNpaSm95275VD92DvJKuyl0s2sFiDmMZ+EnnvufqA==
dependencies:
"@babel/traverse" "^7.1.0"
"@babel/types" "^7.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/helper-function-name@^7.1.0":
version "7.1.0"
resolved "https://registry.yarnpkg.com/@babel/helper-function-name/-/helper-function-name-7.1.0.tgz#a0ceb01685f73355d4360c1247f582bfafc8ff53"
integrity sha512-A95XEoCpb3TO+KZzJ4S/5uW5fNe26DjBGqf1o9ucyLyCmi1dXq/B3c8iaWTfBk3VvetUxl16e8tIrd5teOCfGw==
dependencies:
"@babel/helper-get-function-arity" "^7.0.0"
"@babel/template" "^7.1.0"
"@babel/types" "^7.0.0"
"@babel/helper-get-function-arity@^7.0.0":
version "7.0.0"
resolved "https://registry.yarnpkg.com/@babel/helper-get-function-arity/-/helper-get-function-arity-7.0.0.tgz#83572d4320e2a4657263734113c42868b64e49c3"
integrity sha512-r2DbJeg4svYvt3HOS74U4eWKsUAMRH01Z1ds1zx8KNTPtpTL5JAsdFv8BNyOpVqdFhHkkRDIg5B4AsxmkjAlmQ==
dependencies:
"@babel/types" "^7.0.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/helper-hoist-variables@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/helper-hoist-variables/-/helper-hoist-variables-7.4.4.tgz#0298b5f25c8c09c53102d52ac4a98f773eb2850a"
integrity sha512-VYk2/H/BnYbZDDg39hr3t2kKyifAm1W6zHRfhx8jGjIHpQEBv9dry7oQ2f3+J703TLu69nYdxsovl0XYfcnK4w==
dependencies:
"@babel/types" "^7.4.4"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helper-member-expression-to-functions@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/helper-member-expression-to-functions/-/helper-member-expression-to-functions-7.5.5.tgz#1fb5b8ec4453a93c439ee9fe3aeea4a84b76b590"
integrity sha512-5qZ3D1uMclSNqYcXqiHoA0meVdv+xUEex9em2fqMnrk/scphGlGgg66zjMrPJESPwrFJ6sbfFQYUSa0Mz7FabA==
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
dependencies:
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/types" "^7.5.5"
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/helper-module-imports@^7.0.0":
version "7.0.0"
resolved "https://registry.yarnpkg.com/@babel/helper-module-imports/-/helper-module-imports-7.0.0.tgz#96081b7111e486da4d2cd971ad1a4fe216cc2e3d"
integrity sha512-aP/hlLq01DWNEiDg4Jn23i+CXxW/owM4WpDLFUbpjxe4NS3BhLVZQ5i7E0ZrxuQ/vwekIeciyamgB1UIYxxM6A==
dependencies:
"@babel/types" "^7.0.0"
"@babel/helper-module-transforms@^7.1.0", "@babel/helper-module-transforms@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/helper-module-transforms/-/helper-module-transforms-7.4.4.tgz#96115ea42a2f139e619e98ed46df6019b94414b8"
integrity sha512-3Z1yp8TVQf+B4ynN7WoHPKS8EkdTbgAEy0nU0rs/1Kw4pDgmvYH3rz3aI11KgxKCba2cn7N+tqzV1mY2HMN96w==
dependencies:
"@babel/helper-module-imports" "^7.0.0"
"@babel/helper-simple-access" "^7.1.0"
"@babel/helper-split-export-declaration" "^7.4.4"
"@babel/template" "^7.4.4"
"@babel/types" "^7.4.4"
lodash "^4.17.11"
"@babel/helper-optimise-call-expression@^7.0.0":
version "7.0.0"
resolved "https://registry.yarnpkg.com/@babel/helper-optimise-call-expression/-/helper-optimise-call-expression-7.0.0.tgz#a2920c5702b073c15de51106200aa8cad20497d5"
integrity sha512-u8nd9NQePYNQV8iPWu/pLLYBqZBa4ZaY1YWRFMuxrid94wKI1QNt67NEZ7GAe5Kc/0LLScbim05xZFWkAdrj9g==
dependencies:
"@babel/types" "^7.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/helper-plugin-utils@^7.0.0":
version "7.0.0"
resolved "https://registry.yarnpkg.com/@babel/helper-plugin-utils/-/helper-plugin-utils-7.0.0.tgz#bbb3fbee98661c569034237cc03967ba99b4f250"
integrity sha512-CYAOUCARwExnEixLdB6sDm2dIJ/YgEAKDM1MOeMeZu9Ld/bDgVo8aiWrXwcY7OBh+1Ea2uUcVRcxKk0GJvW7QA==
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/helper-regex@^7.0.0", "@babel/helper-regex@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/helper-regex/-/helper-regex-7.4.4.tgz#a47e02bc91fb259d2e6727c2a30013e3ac13c4a2"
integrity sha512-Y5nuB/kESmR3tKjU8Nkn1wMGEx1tjJX076HBMeL3XLQCu6vA/YRzuTW0bbb+qRnXvQGn+d6Rx953yffl8vEy7Q==
dependencies:
lodash "^4.17.11"
"@babel/helper-remap-async-to-generator@^7.1.0":
version "7.1.0"
resolved "https://registry.yarnpkg.com/@babel/helper-remap-async-to-generator/-/helper-remap-async-to-generator-7.1.0.tgz#361d80821b6f38da75bd3f0785ece20a88c5fe7f"
integrity sha512-3fOK0L+Fdlg8S5al8u/hWE6vhufGSn0bN09xm2LXMy//REAF8kDCrYoOBKYmA8m5Nom+sV9LyLCwrFynA8/slg==
dependencies:
"@babel/helper-annotate-as-pure" "^7.0.0"
"@babel/helper-wrap-function" "^7.1.0"
"@babel/template" "^7.1.0"
"@babel/traverse" "^7.1.0"
"@babel/types" "^7.0.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helper-replace-supers@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/helper-replace-supers/-/helper-replace-supers-7.5.5.tgz#f84ce43df031222d2bad068d2626cb5799c34bc2"
integrity sha512-XvRFWrNnlsow2u7jXDuH4jDDctkxbS7gXssrP4q2nUD606ukXHRvydj346wmNg+zAgpFx4MWf4+usfC93bElJg==
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
dependencies:
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helper-member-expression-to-functions" "^7.5.5"
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/helper-optimise-call-expression" "^7.0.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/traverse" "^7.5.5"
"@babel/types" "^7.5.5"
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/helper-simple-access@^7.1.0":
version "7.1.0"
resolved "https://registry.yarnpkg.com/@babel/helper-simple-access/-/helper-simple-access-7.1.0.tgz#65eeb954c8c245beaa4e859da6188f39d71e585c"
integrity sha512-Vk+78hNjRbsiu49zAPALxTb+JUQCz1aolpd8osOF16BGnLtseD21nbHgLPGUwrXEurZgiCOUmvs3ExTu4F5x6w==
dependencies:
"@babel/template" "^7.1.0"
"@babel/types" "^7.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/helper-split-export-declaration@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/helper-split-export-declaration/-/helper-split-export-declaration-7.4.4.tgz#ff94894a340be78f53f06af038b205c49d993677"
integrity sha512-Ro/XkzLf3JFITkW6b+hNxzZ1n5OQ80NvIUdmHspih1XAhtN3vPTuUFT4eQnela+2MaZ5ulH+iyP513KJrxbN7Q==
dependencies:
"@babel/types" "^7.4.4"
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/helper-wrap-function@^7.1.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/helper-wrap-function/-/helper-wrap-function-7.2.0.tgz#c4e0012445769e2815b55296ead43a958549f6fa"
integrity sha512-o9fP1BZLLSrYlxYEYyl2aS+Flun5gtjTIG8iln+XuEzQTs0PLagAGSXUcqruJwD5fM48jzIEggCKpIfWTcR7pQ==
dependencies:
"@babel/helper-function-name" "^7.1.0"
"@babel/template" "^7.1.0"
"@babel/traverse" "^7.1.0"
"@babel/types" "^7.2.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/helpers@^7.5.0":
Regenerate yarn.lock file (#1204) I've regenerated the yarn.lock file (by removing it and then re-running yarn). This picks up [a fix I authored][fix] for node-eval, which was preventing `yarn test --full` from passing in node 10 and 12. With this upgrde of transitive dependencies, we're now ready to officially support newer versions of node. Test plan: `yarn test` passes.
2019-07-06 14:02:04 +00:00
version "7.5.1"
resolved "https://registry.yarnpkg.com/@babel/helpers/-/helpers-7.5.1.tgz#65407c741a56ddd59dd86346cd112da3de912db3"
integrity sha512-rVOTDv8sH8kNI72Unenusxw6u+1vEepZgLxeV+jHkhsQlYhzVhzL1EpfoWT7Ub3zpWSv2WV03V853dqsnyoQzA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/template" "^7.4.4"
"@babel/traverse" "^7.5.0"
"@babel/types" "^7.5.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helpers@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/helpers/-/helpers-7.5.5.tgz#63908d2a73942229d1e6685bc2a0e730dde3b75e"
integrity sha512-nRq2BUhxZFnfEn/ciJuhklHvFOqjJUD5wpx+1bxUF2axL9C+v4DE/dmp5sT2dKnpOs4orZWzpAZqlCy8QqE/7g==
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
dependencies:
"@babel/template" "^7.4.4"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/traverse" "^7.5.5"
"@babel/types" "^7.5.5"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/highlight@^7.0.0":
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/highlight/-/highlight-7.5.0.tgz#56d11312bd9248fa619591d02472be6e8cb32540"
integrity sha512-7dV4eu9gBxoM0dAnj/BCFDW9LFU0zvTrkq0ugM7pnHEgguOEeOz1so2ZghEdzviYzQEED0r4EAgpsBChKy1TRQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
chalk "^2.0.0"
esutils "^2.0.2"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
js-tokens "^4.0.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
"@babel/parser@^7.0.0", "@babel/parser@^7.1.0", "@babel/parser@^7.4.3", "@babel/parser@^7.4.4", "@babel/parser@^7.5.0":
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.5.0.tgz#3e0713dff89ad6ae37faec3b29dcfc5c979770b7"
integrity sha512-I5nW8AhGpOXGCCNYGc+p7ExQIBxRFnS2fd/d862bNOKvmoEPjYPcfIjsfdy0ujagYOIYPczKgD9l3FsgTkAzKA==
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/parser@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.5.5.tgz#02f077ac8817d3df4a832ef59de67565e71cca4b"
integrity sha512-E5BN68cqR7dhKan1SfqgPGhQ178bkVKpXTPEXnFJBrEt8/DKRZlybmy+IgYLTeN7tp1R5Ccmbm2rBk17sHYU3g==
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/plugin-proposal-async-generator-functions@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.2.0.tgz#b289b306669dce4ad20b0252889a15768c9d417e"
integrity sha512-+Dfo/SCQqrwx48ptLVGLdE39YtWRuKc/Y9I5Fy0P1DDBB9lsAHpjcEJQt+4IifuSOSTLBKJObJqMvaO1pIE8LQ==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/helper-remap-async-to-generator" "^7.1.0"
"@babel/plugin-syntax-async-generators" "^7.2.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/plugin-proposal-class-properties@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-class-properties/-/plugin-proposal-class-properties-7.5.5.tgz#a974cfae1e37c3110e71f3c6a2e48b8e71958cd4"
integrity sha512-AF79FsnWFxjlaosgdi421vmYG6/jg79bVD0dpD44QdgobzHKuLZ6S3vl8la9qIeSwGi8i1fS0O1mfuDAAdo1/A==
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
dependencies:
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helper-create-class-features-plugin" "^7.5.5"
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/helper-plugin-utils" "^7.0.0"
"@babel/plugin-proposal-dynamic-import@^7.5.0":
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-dynamic-import/-/plugin-proposal-dynamic-import-7.5.0.tgz#e532202db4838723691b10a67b8ce509e397c506"
integrity sha512-x/iMjggsKTFHYC6g11PL7Qy58IK8H5zqfm9e6hu4z1iH2IRyAp9u9dL80zA6R76yFovETFLKz2VJIC2iIPBuFw==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-dynamic-import" "^7.2.0"
"@babel/plugin-proposal-json-strings@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-json-strings/-/plugin-proposal-json-strings-7.2.0.tgz#568ecc446c6148ae6b267f02551130891e29f317"
integrity sha512-MAFV1CA/YVmYwZG0fBQyXhmj0BHCB5egZHCKWIFVv/XCxAeVGIHfos3SwDck4LvCllENIAg7xMKOG5kH0dzyUg==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-json-strings" "^7.2.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/plugin-proposal-object-rest-spread@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.5.5.tgz#61939744f71ba76a3ae46b5eea18a54c16d22e58"
integrity sha512-F2DxJJSQ7f64FyTVl5cw/9MWn6naXGdk3Q3UhDbFEEHv+EilCPoeRD3Zh/Utx1CJz4uyKlQ4uH+bJPbEhMV7Zw==
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
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-object-rest-spread" "^7.2.0"
"@babel/plugin-proposal-optional-catch-binding@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-optional-catch-binding/-/plugin-proposal-optional-catch-binding-7.2.0.tgz#135d81edb68a081e55e56ec48541ece8065c38f5"
integrity sha512-mgYj3jCcxug6KUcX4OBoOJz3CMrwRfQELPQ5560F70YQUBZB7uac9fqaWamKR1iWUzGiK2t0ygzjTScZnVz75g==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-optional-catch-binding" "^7.2.0"
"@babel/plugin-proposal-unicode-property-regex@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-proposal-unicode-property-regex/-/plugin-proposal-unicode-property-regex-7.4.4.tgz#501ffd9826c0b91da22690720722ac7cb1ca9c78"
integrity sha512-j1NwnOqMG9mFUOH58JTFsA/+ZYzQLUZ/drqWUqxCYLGeu2JFZL8YrNC9hBxKmWtAuOCHPcRpgv7fhap09Fb4kA==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/helper-regex" "^7.4.4"
regexpu-core "^4.5.4"
"@babel/plugin-syntax-async-generators@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-async-generators/-/plugin-syntax-async-generators-7.2.0.tgz#69e1f0db34c6f5a0cf7e2b3323bf159a76c8cb7f"
integrity sha512-1ZrIRBv2t0GSlcwVoQ6VgSLpLgiN/FVQUzt9znxo7v2Ov4jJrs8RY8tv0wvDmFN3qIdMKWrmMMW6yZ0G19MfGg==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-dynamic-import@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-dynamic-import/-/plugin-syntax-dynamic-import-7.2.0.tgz#69c159ffaf4998122161ad8ebc5e6d1f55df8612"
integrity sha512-mVxuJ0YroI/h/tbFTPGZR8cv6ai+STMKNBq0f8hFxsxWjl94qqhsb+wXbpNMDPU3cfR1TIsVFzU3nXyZMqyK4w==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-flow@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-flow/-/plugin-syntax-flow-7.2.0.tgz#a765f061f803bc48f240c26f8747faf97c26bf7c"
integrity sha512-r6YMuZDWLtLlu0kqIim5o/3TNRAlWb073HwT3e2nKf9I8IIvOggPrnILYPsrrKilmn/mYEMCf/Z07w3yQJF6dg==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-json-strings@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-json-strings/-/plugin-syntax-json-strings-7.2.0.tgz#72bd13f6ffe1d25938129d2a186b11fd62951470"
integrity sha512-5UGYnMSLRE1dqqZwug+1LISpA403HzlSfsg6P9VXU6TBjcSHeNlw4DxDx7LgpF+iKZoOG/+uzqoRHTdcUpiZNg==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-jsx@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-jsx/-/plugin-syntax-jsx-7.2.0.tgz#0b85a3b4bc7cdf4cc4b8bf236335b907ca22e7c7"
integrity sha512-VyN4QANJkRW6lDBmENzRszvZf3/4AXaj9YR7GwrWeeN9tEBPuXbmDYVU9bYBN0D70zCWVwUy0HWq2553VCb6Hw==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-object-rest-spread@^7.0.0", "@babel/plugin-syntax-object-rest-spread@^7.2.0":
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-object-rest-spread/-/plugin-syntax-object-rest-spread-7.2.0.tgz#3b7a3e733510c57e820b9142a6579ac8b0dfad2e"
integrity sha512-t0JKGgqk2We+9may3t0xDdmneaXmyxq0xieYcKHxIsrJO64n1OiMWNUtc5gQK1PA0NpdCRrtZp4z+IUaKugrSA==
dependencies:
"@babel/helper-plugin-utils" "^7.0.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/plugin-syntax-optional-catch-binding@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-optional-catch-binding/-/plugin-syntax-optional-catch-binding-7.2.0.tgz#a94013d6eda8908dfe6a477e7f9eda85656ecf5c"
integrity sha512-bDe4xKNhb0LI7IvZHiA13kff0KEfaGX/Hv4lMA9+7TEc63hMNvfKo6ZFpXhKuEp+II/q35Gc4NoMeDZyaUbj9w==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-arrow-functions@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-arrow-functions/-/plugin-transform-arrow-functions-7.2.0.tgz#9aeafbe4d6ffc6563bf8f8372091628f00779550"
integrity sha512-ER77Cax1+8/8jCB9fo4Ud161OZzWN5qawi4GusDuRLcDbDG+bIGYY20zb2dfAFdTRGzrfq2xZPvF0R64EHnimg==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-async-to-generator@^7.5.0":
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-async-to-generator/-/plugin-transform-async-to-generator-7.5.0.tgz#89a3848a0166623b5bc481164b5936ab947e887e"
integrity sha512-mqvkzwIGkq0bEF1zLRRiTdjfomZJDV33AH3oQzHVGkI2VzEmXLpKKOBvEVaFZBJdN0XTyH38s9j/Kiqr68dggg==
dependencies:
"@babel/helper-module-imports" "^7.0.0"
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/helper-remap-async-to-generator" "^7.1.0"
"@babel/plugin-transform-block-scoped-functions@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoped-functions/-/plugin-transform-block-scoped-functions-7.2.0.tgz#5d3cc11e8d5ddd752aa64c9148d0db6cb79fd190"
integrity sha512-ntQPR6q1/NKuphly49+QiQiTN0O63uOwjdD6dhIjSWBI5xlrbUFh720TIpzBhpnrLfv2tNH/BXvLIab1+BAI0w==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/plugin-transform-block-scoping@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-block-scoping/-/plugin-transform-block-scoping-7.5.5.tgz#a35f395e5402822f10d2119f6f8e045e3639a2ce"
integrity sha512-82A3CLRRdYubkG85lKwhZB0WZoHxLGsJdux/cOVaJCJpvYFl1LVzAIFyRsa7CvXqW8rBM4Zf3Bfn8PHt5DP0Sg==
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
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
lodash "^4.17.13"
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
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/plugin-transform-classes@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-classes/-/plugin-transform-classes-7.5.5.tgz#d094299d9bd680a14a2a0edae38305ad60fb4de9"
integrity sha512-U2htCNK/6e9K7jGyJ++1p5XRU+LJjrwtoiVn9SzRlDT2KubcZ11OOwy3s24TjHxPgxNwonCYP7U2K51uVYCMDg==
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
dependencies:
"@babel/helper-annotate-as-pure" "^7.0.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helper-define-map" "^7.5.5"
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/helper-function-name" "^7.1.0"
"@babel/helper-optimise-call-expression" "^7.0.0"
"@babel/helper-plugin-utils" "^7.0.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helper-replace-supers" "^7.5.5"
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/helper-split-export-declaration" "^7.4.4"
globals "^11.1.0"
"@babel/plugin-transform-computed-properties@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-computed-properties/-/plugin-transform-computed-properties-7.2.0.tgz#83a7df6a658865b1c8f641d510c6f3af220216da"
integrity sha512-kP/drqTxY6Xt3NNpKiMomfgkNn4o7+vKxK2DDKcBG9sHj51vHqMBGy8wbDS/J4lMxnqs153/T3+DmCEAkC5cpA==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-destructuring@^7.5.0":
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-destructuring/-/plugin-transform-destructuring-7.5.0.tgz#f6c09fdfe3f94516ff074fe877db7bc9ef05855a"
integrity sha512-YbYgbd3TryYYLGyC7ZR+Tq8H/+bCmwoaxHfJHupom5ECstzbRLTch6gOQbhEY9Z4hiCNHEURgq06ykFv9JZ/QQ==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-dotall-regex@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-dotall-regex/-/plugin-transform-dotall-regex-7.4.4.tgz#361a148bc951444312c69446d76ed1ea8e4450c3"
integrity sha512-P05YEhRc2h53lZDjRPk/OektxCVevFzZs2Gfjd545Wde3k+yFDbXORgl2e0xpbq8mLcKJ7Idss4fAg0zORN/zg==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/helper-regex" "^7.4.4"
regexpu-core "^4.5.4"
"@babel/plugin-transform-duplicate-keys@^7.5.0":
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-duplicate-keys/-/plugin-transform-duplicate-keys-7.5.0.tgz#c5dbf5106bf84cdf691222c0974c12b1df931853"
integrity sha512-igcziksHizyQPlX9gfSjHkE2wmoCH3evvD2qR5w29/Dk0SMKE/eOI7f1HhBdNhR/zxJDqrgpoDTq5YSLH/XMsQ==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-exponentiation-operator@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-exponentiation-operator/-/plugin-transform-exponentiation-operator-7.2.0.tgz#a63868289e5b4007f7054d46491af51435766008"
integrity sha512-umh4hR6N7mu4Elq9GG8TOu9M0bakvlsREEC+ialrQN6ABS4oDQ69qJv1VtR3uxlKMCQMCvzk7vr17RHKcjx68A==
dependencies:
"@babel/helper-builder-binary-assignment-operator-visitor" "^7.1.0"
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-flow-strip-types@^7.0.0":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-flow-strip-types/-/plugin-transform-flow-strip-types-7.4.4.tgz#d267a081f49a8705fc9146de0768c6b58dccd8f7"
integrity sha512-WyVedfeEIILYEaWGAUWzVNyqG4sfsNooMhXWsu/YzOvVGcsnPb5PguysjJqI3t3qiaYj0BR8T2f5njdjTGe44Q==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-flow" "^7.2.0"
"@babel/plugin-transform-for-of@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-for-of/-/plugin-transform-for-of-7.4.4.tgz#0267fc735e24c808ba173866c6c4d1440fc3c556"
integrity sha512-9T/5Dlr14Z9TIEXLXkt8T1DU7F24cbhwhMNUziN3hB1AXoZcdzPcTiKGRn/6iOymDqtTKWnr/BtRKN9JwbKtdQ==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-function-name@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-function-name/-/plugin-transform-function-name-7.4.4.tgz#e1436116abb0610c2259094848754ac5230922ad"
integrity sha512-iU9pv7U+2jC9ANQkKeNF6DrPy4GBa4NWQtl6dHB4Pb3izX2JOEvDTFarlNsBj/63ZEzNNIAMs3Qw4fNCcSOXJA==
dependencies:
"@babel/helper-function-name" "^7.1.0"
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-literals@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-literals/-/plugin-transform-literals-7.2.0.tgz#690353e81f9267dad4fd8cfd77eafa86aba53ea1"
integrity sha512-2ThDhm4lI4oV7fVQ6pNNK+sx+c/GM5/SaML0w/r4ZB7sAneD/piDJtwdKlNckXeyGK7wlwg2E2w33C/Hh+VFCg==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-member-expression-literals@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-member-expression-literals/-/plugin-transform-member-expression-literals-7.2.0.tgz#fa10aa5c58a2cb6afcf2c9ffa8cb4d8b3d489a2d"
integrity sha512-HiU3zKkSU6scTidmnFJ0bMX8hz5ixC93b4MHMiYebmk2lUVNGOboPsqQvx5LzooihijUoLR/v7Nc1rbBtnc7FA==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-modules-amd@^7.5.0":
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-amd/-/plugin-transform-modules-amd-7.5.0.tgz#ef00435d46da0a5961aa728a1d2ecff063e4fb91"
integrity sha512-n20UsQMKnWrltocZZm24cRURxQnWIvsABPJlw/fvoy9c6AgHZzoelAIzajDHAQrDpuKFFPPcFGd7ChsYuIUMpg==
dependencies:
"@babel/helper-module-transforms" "^7.1.0"
"@babel/helper-plugin-utils" "^7.0.0"
babel-plugin-dynamic-import-node "^2.3.0"
"@babel/plugin-transform-modules-commonjs@^7.5.0":
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-commonjs/-/plugin-transform-modules-commonjs-7.5.0.tgz#425127e6045231360858eeaa47a71d75eded7a74"
integrity sha512-xmHq0B+ytyrWJvQTc5OWAC4ii6Dhr0s22STOoydokG51JjWhyYo5mRPXoi+ZmtHQhZZwuXNN+GG5jy5UZZJxIQ==
dependencies:
"@babel/helper-module-transforms" "^7.4.4"
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/helper-simple-access" "^7.1.0"
babel-plugin-dynamic-import-node "^2.3.0"
"@babel/plugin-transform-modules-systemjs@^7.5.0":
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-systemjs/-/plugin-transform-modules-systemjs-7.5.0.tgz#e75266a13ef94202db2a0620977756f51d52d249"
integrity sha512-Q2m56tyoQWmuNGxEtUyeEkm6qJYFqs4c+XyXH5RAuYxObRNz9Zgj/1g2GMnjYp2EUyEy7YTrxliGCXzecl/vJg==
dependencies:
"@babel/helper-hoist-variables" "^7.4.4"
"@babel/helper-plugin-utils" "^7.0.0"
babel-plugin-dynamic-import-node "^2.3.0"
"@babel/plugin-transform-modules-umd@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-modules-umd/-/plugin-transform-modules-umd-7.2.0.tgz#7678ce75169f0877b8eb2235538c074268dd01ae"
integrity sha512-BV3bw6MyUH1iIsGhXlOK6sXhmSarZjtJ/vMiD9dNmpY8QXFFQTj+6v92pcfy1iqa8DeAfJFwoxcrS/TUZda6sw==
dependencies:
"@babel/helper-module-transforms" "^7.1.0"
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-named-capturing-groups-regex@^7.4.5":
version "7.4.5"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-named-capturing-groups-regex/-/plugin-transform-named-capturing-groups-regex-7.4.5.tgz#9d269fd28a370258199b4294736813a60bbdd106"
integrity sha512-z7+2IsWafTBbjNsOxU/Iv5CvTJlr5w4+HGu1HovKYTtgJ362f7kBcQglkfmlspKKZ3bgrbSGvLfNx++ZJgCWsg==
dependencies:
regexp-tree "^0.1.6"
"@babel/plugin-transform-new-target@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-new-target/-/plugin-transform-new-target-7.4.4.tgz#18d120438b0cc9ee95a47f2c72bc9768fbed60a5"
integrity sha512-r1z3T2DNGQwwe2vPGZMBNjioT2scgWzK9BCnDEh+46z8EEwXBq24uRzd65I7pjtugzPSj921aM15RpESgzsSuA==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/plugin-transform-object-super@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-object-super/-/plugin-transform-object-super-7.5.5.tgz#c70021df834073c65eb613b8679cc4a381d1a9f9"
integrity sha512-un1zJQAhSosGFBduPgN/YFNvWVpRuHKU7IHBglLoLZsGmruJPOo6pbInneflUdmq7YvSVqhpPs5zdBvLnteltQ==
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
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/helper-replace-supers" "^7.5.5"
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/plugin-transform-parameters@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-parameters/-/plugin-transform-parameters-7.4.4.tgz#7556cf03f318bd2719fe4c922d2d808be5571e16"
integrity sha512-oMh5DUO1V63nZcu/ZVLQFqiihBGo4OpxJxR1otF50GMeCLiRx5nUdtokd+u9SuVJrvvuIh9OosRFPP4pIPnwmw==
dependencies:
"@babel/helper-call-delegate" "^7.4.4"
"@babel/helper-get-function-arity" "^7.0.0"
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-property-literals@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-property-literals/-/plugin-transform-property-literals-7.2.0.tgz#03e33f653f5b25c4eb572c98b9485055b389e905"
integrity sha512-9q7Dbk4RhgcLp8ebduOpCbtjh7C0itoLYHXd9ueASKAG/is5PQtMR5VJGka9NKqGhYEGn5ITahd4h9QeBMylWQ==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-react-display-name@^7.0.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-display-name/-/plugin-transform-react-display-name-7.2.0.tgz#ebfaed87834ce8dc4279609a4f0c324c156e3eb0"
integrity sha512-Htf/tPa5haZvRMiNSQSFifK12gtr/8vwfr+A9y69uF0QcU77AVu4K7MiHEkTxF7lQoHOL0F9ErqgfNEAKgXj7A==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-react-jsx-self@^7.0.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-jsx-self/-/plugin-transform-react-jsx-self-7.2.0.tgz#461e21ad9478f1031dd5e276108d027f1b5240ba"
integrity sha512-v6S5L/myicZEy+jr6ielB0OR8h+EH/1QFx/YJ7c7Ua+7lqsjj/vW6fD5FR9hB/6y7mGbfT4vAURn3xqBxsUcdg==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-jsx" "^7.2.0"
"@babel/plugin-transform-react-jsx-source@^7.0.0":
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-jsx-source/-/plugin-transform-react-jsx-source-7.5.0.tgz#583b10c49cf057e237085bcbd8cc960bd83bd96b"
integrity sha512-58Q+Jsy4IDCZx7kqEZuSDdam/1oW8OdDX8f+Loo6xyxdfg1yF0GE2XNJQSTZCaMol93+FBzpWiPEwtbMloAcPg==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-jsx" "^7.2.0"
"@babel/plugin-transform-react-jsx@^7.0.0":
version "7.3.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-react-jsx/-/plugin-transform-react-jsx-7.3.0.tgz#f2cab99026631c767e2745a5368b331cfe8f5290"
integrity sha512-a/+aRb7R06WcKvQLOu4/TpjKOdvVEKRLWFpKcNuHhiREPgGRB4TQJxq07+EZLS8LFVYpfq1a5lDUnuMdcCpBKg==
dependencies:
"@babel/helper-builder-react-jsx" "^7.3.0"
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-syntax-jsx" "^7.2.0"
"@babel/plugin-transform-regenerator@^7.4.5":
version "7.4.5"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-regenerator/-/plugin-transform-regenerator-7.4.5.tgz#629dc82512c55cee01341fb27bdfcb210354680f"
integrity sha512-gBKRh5qAaCWntnd09S8QC7r3auLCqq5DI6O0DlfoyDjslSBVqBibrMdsqO+Uhmx3+BlOmE/Kw1HFxmGbv0N9dA==
dependencies:
regenerator-transform "^0.14.0"
"@babel/plugin-transform-reserved-words@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-reserved-words/-/plugin-transform-reserved-words-7.2.0.tgz#4792af87c998a49367597d07fedf02636d2e1634"
integrity sha512-fz43fqW8E1tAB3DKF19/vxbpib1fuyCwSPE418ge5ZxILnBhWyhtPgz8eh1RCGGJlwvksHkyxMxh0eenFi+kFw==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-shorthand-properties@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-shorthand-properties/-/plugin-transform-shorthand-properties-7.2.0.tgz#6333aee2f8d6ee7e28615457298934a3b46198f0"
integrity sha512-QP4eUM83ha9zmYtpbnyjTLAGKQritA5XW/iG9cjtuOI8s1RuL/3V6a3DeSHfKutJQ+ayUfeZJPcnCYEQzaPQqg==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-spread@^7.2.0":
version "7.2.2"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-spread/-/plugin-transform-spread-7.2.2.tgz#3103a9abe22f742b6d406ecd3cd49b774919b406"
integrity sha512-KWfky/58vubwtS0hLqEnrWJjsMGaOeSBn90Ezn5Jeg9Z8KKHmELbP1yGylMlm5N6TPKeY9A2+UaSYLdxahg01w==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-sticky-regex@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-sticky-regex/-/plugin-transform-sticky-regex-7.2.0.tgz#a1e454b5995560a9c1e0d537dfc15061fd2687e1"
integrity sha512-KKYCoGaRAf+ckH8gEL3JHUaFVyNHKe3ASNsZ+AlktgHevvxGigoIttrEJb8iKN03Q7Eazlv1s6cx2B2cQ3Jabw==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/helper-regex" "^7.0.0"
"@babel/plugin-transform-template-literals@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-template-literals/-/plugin-transform-template-literals-7.4.4.tgz#9d28fea7bbce637fb7612a0750989d8321d4bcb0"
integrity sha512-mQrEC4TWkhLN0z8ygIvEL9ZEToPhG5K7KDW3pzGqOfIGZ28Jb0POUkeWcoz8HnHvhFy6dwAT1j8OzqN8s804+g==
dependencies:
"@babel/helper-annotate-as-pure" "^7.0.0"
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-typeof-symbol@^7.2.0":
version "7.2.0"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-typeof-symbol/-/plugin-transform-typeof-symbol-7.2.0.tgz#117d2bcec2fbf64b4b59d1f9819894682d29f2b2"
integrity sha512-2LNhETWYxiYysBtrBTqL8+La0jIoQQnIScUJc74OYvUGRmkskNY4EzLCnjHBzdmb38wqtTaixpo1NctEcvMDZw==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-unicode-regex@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-transform-unicode-regex/-/plugin-transform-unicode-regex-7.4.4.tgz#ab4634bb4f14d36728bf5978322b35587787970f"
integrity sha512-il+/XdNw01i93+M9J9u4T7/e/Ue/vWfNZE4IRUQjplu2Mqb/AFTDimkw2tdEdSH50wuQXZAbXSql0UphQke+vA==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/helper-regex" "^7.4.4"
regexpu-core "^4.5.4"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/preset-env@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/preset-env/-/preset-env-7.5.5.tgz#bc470b53acaa48df4b8db24a570d6da1fef53c9a"
integrity sha512-GMZQka/+INwsMz1A5UEql8tG015h5j/qjptpKY2gJ7giy8ohzU710YciJB5rcKsWGWHiW3RUnHib0E5/m3Tp3A==
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
dependencies:
"@babel/helper-module-imports" "^7.0.0"
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-proposal-async-generator-functions" "^7.2.0"
"@babel/plugin-proposal-dynamic-import" "^7.5.0"
"@babel/plugin-proposal-json-strings" "^7.2.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/plugin-proposal-object-rest-spread" "^7.5.5"
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/plugin-proposal-optional-catch-binding" "^7.2.0"
"@babel/plugin-proposal-unicode-property-regex" "^7.4.4"
"@babel/plugin-syntax-async-generators" "^7.2.0"
"@babel/plugin-syntax-dynamic-import" "^7.2.0"
"@babel/plugin-syntax-json-strings" "^7.2.0"
"@babel/plugin-syntax-object-rest-spread" "^7.2.0"
"@babel/plugin-syntax-optional-catch-binding" "^7.2.0"
"@babel/plugin-transform-arrow-functions" "^7.2.0"
"@babel/plugin-transform-async-to-generator" "^7.5.0"
"@babel/plugin-transform-block-scoped-functions" "^7.2.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/plugin-transform-block-scoping" "^7.5.5"
"@babel/plugin-transform-classes" "^7.5.5"
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/plugin-transform-computed-properties" "^7.2.0"
"@babel/plugin-transform-destructuring" "^7.5.0"
"@babel/plugin-transform-dotall-regex" "^7.4.4"
"@babel/plugin-transform-duplicate-keys" "^7.5.0"
"@babel/plugin-transform-exponentiation-operator" "^7.2.0"
"@babel/plugin-transform-for-of" "^7.4.4"
"@babel/plugin-transform-function-name" "^7.4.4"
"@babel/plugin-transform-literals" "^7.2.0"
"@babel/plugin-transform-member-expression-literals" "^7.2.0"
"@babel/plugin-transform-modules-amd" "^7.5.0"
"@babel/plugin-transform-modules-commonjs" "^7.5.0"
"@babel/plugin-transform-modules-systemjs" "^7.5.0"
"@babel/plugin-transform-modules-umd" "^7.2.0"
"@babel/plugin-transform-named-capturing-groups-regex" "^7.4.5"
"@babel/plugin-transform-new-target" "^7.4.4"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/plugin-transform-object-super" "^7.5.5"
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/plugin-transform-parameters" "^7.4.4"
"@babel/plugin-transform-property-literals" "^7.2.0"
"@babel/plugin-transform-regenerator" "^7.4.5"
"@babel/plugin-transform-reserved-words" "^7.2.0"
"@babel/plugin-transform-shorthand-properties" "^7.2.0"
"@babel/plugin-transform-spread" "^7.2.0"
"@babel/plugin-transform-sticky-regex" "^7.2.0"
"@babel/plugin-transform-template-literals" "^7.4.4"
"@babel/plugin-transform-typeof-symbol" "^7.2.0"
"@babel/plugin-transform-unicode-regex" "^7.4.4"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/types" "^7.5.5"
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
browserslist "^4.6.0"
core-js-compat "^3.1.1"
invariant "^2.2.2"
js-levenshtein "^1.1.3"
semver "^5.5.0"
"@babel/preset-flow@^7.0.0":
version "7.0.0"
resolved "https://registry.yarnpkg.com/@babel/preset-flow/-/preset-flow-7.0.0.tgz#afd764835d9535ec63d8c7d4caf1c06457263da2"
integrity sha512-bJOHrYOPqJZCkPVbG1Lot2r5OSsB+iUOaxiHdlOeB1yPWS6evswVHwvkDLZ54WTaTRIk89ds0iHmGZSnxlPejQ==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-flow-strip-types" "^7.0.0"
"@babel/preset-react@^7.0.0":
version "7.0.0"
resolved "https://registry.yarnpkg.com/@babel/preset-react/-/preset-react-7.0.0.tgz#e86b4b3d99433c7b3e9e91747e2653958bc6b3c0"
integrity sha512-oayxyPS4Zj+hF6Et11BwuBkmpgT/zMxyuZgFrMeZID6Hdh3dGlk4sHCAhdBCpuCKW2ppBfl2uCCetlrUIJRY3w==
dependencies:
"@babel/helper-plugin-utils" "^7.0.0"
"@babel/plugin-transform-react-display-name" "^7.0.0"
"@babel/plugin-transform-react-jsx" "^7.0.0"
"@babel/plugin-transform-react-jsx-self" "^7.0.0"
"@babel/plugin-transform-react-jsx-source" "^7.0.0"
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
"@babel/runtime@^7.1.2":
version "7.4.5"
resolved "https://registry.yarnpkg.com/@babel/runtime/-/runtime-7.4.5.tgz#582bb531f5f9dc67d2fcb682979894f75e253f12"
integrity sha512-TuI4qpWZP6lGOGIuGWtp9sPluqYICmbk8T/1vpSysqJxRPkudh/ofFWyqdcMsDf2s7KvDL4/YHgKyvcS3g9CJQ==
dependencies:
regenerator-runtime "^0.13.2"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
"@babel/runtime@^7.4.5":
Regenerate yarn.lock file (#1204) I've regenerated the yarn.lock file (by removing it and then re-running yarn). This picks up [a fix I authored][fix] for node-eval, which was preventing `yarn test --full` from passing in node 10 and 12. With this upgrde of transitive dependencies, we're now ready to officially support newer versions of node. Test plan: `yarn test` passes.
2019-07-06 14:02:04 +00:00
version "7.5.1"
resolved "https://registry.yarnpkg.com/@babel/runtime/-/runtime-7.5.1.tgz#51b56e216e87103ab3f7d6040b464c538e242888"
integrity sha512-g+hmPKs16iewFSmW57NkH9xpPkuYD1RV3UE2BCkXx9j+nhhRb9hsiSxPmEa67j35IecTQdn4iyMtHMbt5VoREg==
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
dependencies:
regenerator-runtime "^0.13.2"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/template@^7.1.0", "@babel/template@^7.4.0", "@babel/template@^7.4.4":
version "7.4.4"
resolved "https://registry.yarnpkg.com/@babel/template/-/template-7.4.4.tgz#f4b88d1225689a08f5bc3a17483545be9e4ed237"
integrity sha512-CiGzLN9KgAvgZsnivND7rkA+AeJ9JB0ciPOD4U59GKbQP2iQl+olF1l76kJOupqidozfZ32ghwBEJDhnk9MEcw==
dependencies:
"@babel/code-frame" "^7.0.0"
"@babel/parser" "^7.4.4"
"@babel/types" "^7.4.4"
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/traverse@^7.0.0", "@babel/traverse@^7.1.0", "@babel/traverse@^7.4.3", "@babel/traverse@^7.4.4", "@babel/traverse@^7.5.0":
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.5.0.tgz#4216d6586854ef5c3c4592dab56ec7eb78485485"
integrity sha512-SnA9aLbyOCcnnbQEGwdfBggnc142h/rbqqsXcaATj2hZcegCl903pUD/lfpsNBlBSuWow/YDfRyJuWi2EPR5cg==
dependencies:
"@babel/code-frame" "^7.0.0"
"@babel/generator" "^7.5.0"
"@babel/helper-function-name" "^7.1.0"
"@babel/helper-split-export-declaration" "^7.4.4"
"@babel/parser" "^7.5.0"
"@babel/types" "^7.5.0"
debug "^4.1.0"
globals "^11.1.0"
lodash "^4.17.11"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/traverse@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.5.5.tgz#f664f8f368ed32988cd648da9f72d5ca70f165bb"
integrity sha512-MqB0782whsfffYfSjH4TM+LMjrJnhCNEDMDIjeTpl+ASaUvxcjoiVCo/sM1GhS1pHOXYfWVCYneLjMckuUxDaQ==
dependencies:
"@babel/code-frame" "^7.5.5"
"@babel/generator" "^7.5.5"
"@babel/helper-function-name" "^7.1.0"
"@babel/helper-split-export-declaration" "^7.4.4"
"@babel/parser" "^7.5.5"
"@babel/types" "^7.5.5"
debug "^4.1.0"
globals "^11.1.0"
lodash "^4.17.13"
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/types@^7.0.0", "@babel/types@^7.2.0", "@babel/types@^7.3.0", "@babel/types@^7.4.0", "@babel/types@^7.4.4", "@babel/types@^7.5.0":
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "7.5.0"
resolved "https://registry.yarnpkg.com/@babel/types/-/types-7.5.0.tgz#e47d43840c2e7f9105bc4d3a2c371b4d0c7832ab"
integrity sha512-UFpDVqRABKsW01bvw7/wSUe56uy6RXM5+VJibVVAybDGxEW25jdwiFJEf7ASvSaC7sN7rbE/l3cLp2izav+CtQ==
dependencies:
esutils "^2.0.2"
lodash "^4.17.11"
to-fast-properties "^2.0.0"
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
"@babel/types@^7.5.5":
version "7.5.5"
resolved "https://registry.yarnpkg.com/@babel/types/-/types-7.5.5.tgz#97b9f728e182785909aa4ab56264f090a028d18a"
integrity sha512-s63F9nJioLqOlW3UkyMd+BYhXt44YuaFm/VV0VwuteqjYwRrObkU7ra9pY4wAJR3oXi8hJrMcrcJdO/HH33vtw==
dependencies:
esutils "^2.0.2"
lodash "^4.17.13"
to-fast-properties "^2.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@cnakazawa/watch@^1.0.3":
version "1.0.3"
resolved "https://registry.yarnpkg.com/@cnakazawa/watch/-/watch-1.0.3.tgz#099139eaec7ebf07a27c1786a3ff64f39464d2ef"
integrity sha512-r5160ogAvGyHsal38Kux7YYtodEKOj89RGb28ht1jh3SJb08VwRwAKKJL0bGb04Zd/3r9FL3BFIc3bBidYffCA==
dependencies:
exec-sh "^0.3.2"
minimist "^1.2.0"
"@jest/console@^24.7.1":
version "24.7.1"
resolved "https://registry.yarnpkg.com/@jest/console/-/console-24.7.1.tgz#32a9e42535a97aedfe037e725bd67e954b459545"
integrity sha512-iNhtIy2M8bXlAOULWVTUxmnelTLFneTNEkHCgPmgd+zNwy9zVddJ6oS5rZ9iwoscNdT5mMwUd0C51v/fSlzItg==
dependencies:
"@jest/source-map" "^24.3.0"
chalk "^2.0.1"
slash "^2.0.0"
"@jest/core@^24.8.0":
version "24.8.0"
resolved "https://registry.yarnpkg.com/@jest/core/-/core-24.8.0.tgz#fbbdcd42a41d0d39cddbc9f520c8bab0c33eed5b"
integrity sha512-R9rhAJwCBQzaRnrRgAdVfnglUuATXdwTRsYqs6NMdVcAl5euG8LtWDe+fVkN27YfKVBW61IojVsXKaOmSnqd/A==
dependencies:
"@jest/console" "^24.7.1"
"@jest/reporters" "^24.8.0"
"@jest/test-result" "^24.8.0"
"@jest/transform" "^24.8.0"
"@jest/types" "^24.8.0"
ansi-escapes "^3.0.0"
chalk "^2.0.1"
exit "^0.1.2"
graceful-fs "^4.1.15"
jest-changed-files "^24.8.0"
jest-config "^24.8.0"
jest-haste-map "^24.8.0"
jest-message-util "^24.8.0"
jest-regex-util "^24.3.0"
jest-resolve-dependencies "^24.8.0"
jest-runner "^24.8.0"
jest-runtime "^24.8.0"
jest-snapshot "^24.8.0"
jest-util "^24.8.0"
jest-validate "^24.8.0"
jest-watcher "^24.8.0"
micromatch "^3.1.10"
p-each-series "^1.0.0"
pirates "^4.0.1"
realpath-native "^1.1.0"
rimraf "^2.5.4"
strip-ansi "^5.0.0"
"@jest/environment@^24.8.0":
version "24.8.0"
resolved "https://registry.yarnpkg.com/@jest/environment/-/environment-24.8.0.tgz#0342261383c776bdd652168f68065ef144af0eac"
integrity sha512-vlGt2HLg7qM+vtBrSkjDxk9K0YtRBi7HfRFaDxoRtyi+DyVChzhF20duvpdAnKVBV6W5tym8jm0U9EfXbDk1tw==
dependencies:
"@jest/fake-timers" "^24.8.0"
"@jest/transform" "^24.8.0"
"@jest/types" "^24.8.0"
jest-mock "^24.8.0"
"@jest/fake-timers@^24.8.0":
version "24.8.0"
resolved "https://registry.yarnpkg.com/@jest/fake-timers/-/fake-timers-24.8.0.tgz#2e5b80a4f78f284bcb4bd5714b8e10dd36a8d3d1"
integrity sha512-2M4d5MufVXwi6VzZhJ9f5S/wU4ud2ck0kxPof1Iz3zWx6Y+V2eJrES9jEktB6O3o/oEyk+il/uNu9PvASjWXQw==
dependencies:
"@jest/types" "^24.8.0"
jest-message-util "^24.8.0"
jest-mock "^24.8.0"
"@jest/reporters@^24.8.0":
version "24.8.0"
resolved "https://registry.yarnpkg.com/@jest/reporters/-/reporters-24.8.0.tgz#075169cd029bddec54b8f2c0fc489fd0b9e05729"
integrity sha512-eZ9TyUYpyIIXfYCrw0UHUWUvE35vx5I92HGMgS93Pv7du+GHIzl+/vh8Qj9MCWFK/4TqyttVBPakWMOfZRIfxw==
dependencies:
"@jest/environment" "^24.8.0"
"@jest/test-result" "^24.8.0"
"@jest/transform" "^24.8.0"
"@jest/types" "^24.8.0"
chalk "^2.0.1"
exit "^0.1.2"
glob "^7.1.2"
istanbul-lib-coverage "^2.0.2"
istanbul-lib-instrument "^3.0.1"
istanbul-lib-report "^2.0.4"
istanbul-lib-source-maps "^3.0.1"
istanbul-reports "^2.1.1"
jest-haste-map "^24.8.0"
jest-resolve "^24.8.0"
jest-runtime "^24.8.0"
jest-util "^24.8.0"
jest-worker "^24.6.0"
node-notifier "^5.2.1"
slash "^2.0.0"
source-map "^0.6.0"
string-length "^2.0.0"
"@jest/source-map@^24.3.0":
version "24.3.0"
resolved "https://registry.yarnpkg.com/@jest/source-map/-/source-map-24.3.0.tgz#563be3aa4d224caf65ff77edc95cd1ca4da67f28"
integrity sha512-zALZt1t2ou8le/crCeeiRYzvdnTzaIlpOWaet45lNSqNJUnXbppUUFR4ZUAlzgDmKee4Q5P/tKXypI1RiHwgag==
dependencies:
callsites "^3.0.0"
graceful-fs "^4.1.15"
source-map "^0.6.0"
"@jest/test-result@^24.8.0":
version "24.8.0"
resolved "https://registry.yarnpkg.com/@jest/test-result/-/test-result-24.8.0.tgz#7675d0aaf9d2484caa65e048d9b467d160f8e9d3"
integrity sha512-+YdLlxwizlfqkFDh7Mc7ONPQAhA4YylU1s529vVM1rsf67vGZH/2GGm5uO8QzPeVyaVMobCQ7FTxl38QrKRlng==
dependencies:
"@jest/console" "^24.7.1"
"@jest/types" "^24.8.0"
"@types/istanbul-lib-coverage" "^2.0.0"
"@jest/test-sequencer@^24.8.0":
version "24.8.0"
resolved "https://registry.yarnpkg.com/@jest/test-sequencer/-/test-sequencer-24.8.0.tgz#2f993bcf6ef5eb4e65e8233a95a3320248cf994b"
integrity sha512-OzL/2yHyPdCHXEzhoBuq37CE99nkme15eHkAzXRVqthreWZamEMA0WoetwstsQBCXABhczpK03JNbc4L01vvLg==
dependencies:
"@jest/test-result" "^24.8.0"
jest-haste-map "^24.8.0"
jest-runner "^24.8.0"
jest-runtime "^24.8.0"
"@jest/transform@^24.8.0":
version "24.8.0"
resolved "https://registry.yarnpkg.com/@jest/transform/-/transform-24.8.0.tgz#628fb99dce4f9d254c6fd9341e3eea262e06fef5"
integrity sha512-xBMfFUP7TortCs0O+Xtez2W7Zu1PLH9bvJgtraN1CDST6LBM/eTOZ9SfwS/lvV8yOfcDpFmwf9bq5cYbXvqsvA==
dependencies:
"@babel/core" "^7.1.0"
"@jest/types" "^24.8.0"
babel-plugin-istanbul "^5.1.0"
chalk "^2.0.1"
convert-source-map "^1.4.0"
fast-json-stable-stringify "^2.0.0"
graceful-fs "^4.1.15"
jest-haste-map "^24.8.0"
jest-regex-util "^24.3.0"
jest-util "^24.8.0"
micromatch "^3.1.10"
realpath-native "^1.1.0"
slash "^2.0.0"
source-map "^0.6.1"
write-file-atomic "2.4.1"
"@jest/types@^24.8.0":
version "24.8.0"
resolved "https://registry.yarnpkg.com/@jest/types/-/types-24.8.0.tgz#f31e25948c58f0abd8c845ae26fcea1491dea7ad"
integrity sha512-g17UxVr2YfBtaMUxn9u/4+siG1ptg9IGYAYwvpwn61nBg779RXnjE/m7CxYcIzEt0AbHZZAHSEZNhkE2WxURVg==
dependencies:
"@types/istanbul-lib-coverage" "^2.0.0"
"@types/istanbul-reports" "^1.1.1"
"@types/yargs" "^12.0.9"
"@types/babel__core@^7.1.0":
version "7.1.2"
resolved "https://registry.yarnpkg.com/@types/babel__core/-/babel__core-7.1.2.tgz#608c74f55928033fce18b99b213c16be4b3d114f"
integrity sha512-cfCCrFmiGY/yq0NuKNxIQvZFy9kY/1immpSpTngOnyIbD4+eJOG5mxphhHDv3CHL9GltO4GcKr54kGBg3RNdbg==
dependencies:
"@babel/parser" "^7.1.0"
"@babel/types" "^7.0.0"
"@types/babel__generator" "*"
"@types/babel__template" "*"
"@types/babel__traverse" "*"
"@types/babel__generator@*":
version "7.0.2"
resolved "https://registry.yarnpkg.com/@types/babel__generator/-/babel__generator-7.0.2.tgz#d2112a6b21fad600d7674274293c85dce0cb47fc"
integrity sha512-NHcOfab3Zw4q5sEE2COkpfXjoE7o+PmqD9DQW4koUT3roNxwziUdXGnRndMat/LJNUtePwn1TlP4do3uoe3KZQ==
dependencies:
"@babel/types" "^7.0.0"
"@types/babel__template@*":
version "7.0.2"
resolved "https://registry.yarnpkg.com/@types/babel__template/-/babel__template-7.0.2.tgz#4ff63d6b52eddac1de7b975a5223ed32ecea9307"
integrity sha512-/K6zCpeW7Imzgab2bLkLEbz0+1JlFSrUMdw7KoIIu+IUdu51GWaBZpd3y1VXGVXzynvGa4DaIaxNZHiON3GXUg==
dependencies:
"@babel/parser" "^7.1.0"
"@babel/types" "^7.0.0"
"@types/babel__traverse@*", "@types/babel__traverse@^7.0.6":
version "7.0.7"
resolved "https://registry.yarnpkg.com/@types/babel__traverse/-/babel__traverse-7.0.7.tgz#2496e9ff56196cc1429c72034e07eab6121b6f3f"
integrity sha512-CeBpmX1J8kWLcDEnI3Cl2Eo6RfbGvzUctA+CjZUhOKDFbLfcr7fc4usEqLNWetrlJd7RhAkyYe2czXop4fICpw==
dependencies:
"@babel/types" "^7.3.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
"@types/events@*":
version "3.0.0"
resolved "https://registry.yarnpkg.com/@types/events/-/events-3.0.0.tgz#2862f3f58a9a7f7c3e78d79f130dd4d71c25c2a7"
integrity sha512-EaObqwIvayI5a8dCzhFrjKzVwKLxjoG9T6Ppd5CEo07LRKfQ8Yokw54r5+Wq7FaBQ+yXRvQAYPrHwya1/UFt9g==
"@types/glob@^7.1.1":
version "7.1.1"
resolved "https://registry.yarnpkg.com/@types/glob/-/glob-7.1.1.tgz#aa59a1c6e3fbc421e07ccd31a944c30eba521575"
integrity sha512-1Bh06cbWJUHMC97acuD6UMG29nMt0Aqz1vF3guLfG+kHHJhy3AyohZFFxYk2f7Q1SQIrNwvncxAE0N/9s70F2w==
dependencies:
"@types/events" "*"
"@types/minimatch" "*"
"@types/node" "*"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@types/istanbul-lib-coverage@*", "@types/istanbul-lib-coverage@^2.0.0":
version "2.0.1"
resolved "https://registry.yarnpkg.com/@types/istanbul-lib-coverage/-/istanbul-lib-coverage-2.0.1.tgz#42995b446db9a48a11a07ec083499a860e9138ff"
integrity sha512-hRJD2ahnnpLgsj6KWMYSrmXkM3rm2Dl1qkx6IOFD5FnuNPXJIG5L0dhgKXCYTRMGzU4n0wImQ/xfmRc4POUFlg==
"@types/istanbul-lib-report@*":
version "1.1.1"
resolved "https://registry.yarnpkg.com/@types/istanbul-lib-report/-/istanbul-lib-report-1.1.1.tgz#e5471e7fa33c61358dd38426189c037a58433b8c"
integrity sha512-3BUTyMzbZa2DtDI2BkERNC6jJw2Mr2Y0oGI7mRxYNBPxppbtEK1F66u3bKwU2g+wxwWI7PAoRpJnOY1grJqzHg==
dependencies:
"@types/istanbul-lib-coverage" "*"
"@types/istanbul-reports@^1.1.1":
version "1.1.1"
resolved "https://registry.yarnpkg.com/@types/istanbul-reports/-/istanbul-reports-1.1.1.tgz#7a8cbf6a406f36c8add871625b278eaf0b0d255a"
integrity sha512-UpYjBi8xefVChsCoBpKShdxTllC9pwISirfoZsUa2AAdQg/Jd2KQGtSbw+ya7GPo7x/wAPlH6JBhKhAsXUEZNA==
dependencies:
"@types/istanbul-lib-coverage" "*"
"@types/istanbul-lib-report" "*"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
"@types/minimatch@*":
version "3.0.3"
resolved "https://registry.yarnpkg.com/@types/minimatch/-/minimatch-3.0.3.tgz#3dca0e3f33b200fc7d1139c0cd96c1268cadfd9d"
integrity sha512-tHq6qdbT9U1IRSGf14CL0pUlULksvY9OZ+5eEgl1N7t+OA3tGvNpxJCzuKQlsNgCVwbAs670L1vcVQi8j9HjnA==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
"@types/node@*":
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "12.0.12"
resolved "https://registry.yarnpkg.com/@types/node/-/node-12.0.12.tgz#cc791b402360db1eaf7176479072f91ee6c6c7ca"
integrity sha512-Uy0PN4R5vgBUXFoJrKryf5aTk3kJ8Rv3PdlHjl6UaX+Cqp1QE0yPQ68MPXGrZOfG7gZVNDIJZYyot0B9ubXUrQ==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@types/stack-utils@^1.0.1":
version "1.0.1"
resolved "https://registry.yarnpkg.com/@types/stack-utils/-/stack-utils-1.0.1.tgz#0a851d3bd96498fa25c33ab7278ed3bd65f06c3e"
integrity sha512-l42BggppR6zLmpfU6fq9HEa2oGPEI8yrSPL3GITjfRInppYFahObbIQOQK3UGxEnyQpltZLaPe75046NOZQikw==
"@types/yargs@^12.0.2", "@types/yargs@^12.0.9":
version "12.0.12"
resolved "https://registry.yarnpkg.com/@types/yargs/-/yargs-12.0.12.tgz#45dd1d0638e8c8f153e87d296907659296873916"
integrity sha512-SOhuU4wNBxhhTHxYaiG5NY4HBhDIDnJF60GU+2LqHAdKKer86//e4yg69aENCtQ04n0ovz+tq2YPME5t5yp4pw==
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
"@webassemblyjs/ast@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/ast/-/ast-1.8.5.tgz#51b1c5fe6576a34953bf4b253df9f0d490d9e359"
integrity sha512-aJMfngIZ65+t71C3y2nBBg5FFG0Okt9m0XEgWZ7Ywgn1oMAT8cNwx00Uv1cQyHtidq0Xn94R4TAywO+LCQ+ZAQ==
dependencies:
"@webassemblyjs/helper-module-context" "1.8.5"
"@webassemblyjs/helper-wasm-bytecode" "1.8.5"
"@webassemblyjs/wast-parser" "1.8.5"
"@webassemblyjs/floating-point-hex-parser@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/floating-point-hex-parser/-/floating-point-hex-parser-1.8.5.tgz#1ba926a2923613edce496fd5b02e8ce8a5f49721"
integrity sha512-9p+79WHru1oqBh9ewP9zW95E3XAo+90oth7S5Re3eQnECGq59ly1Ri5tsIipKGpiStHsUYmY3zMLqtk3gTcOtQ==
"@webassemblyjs/helper-api-error@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-api-error/-/helper-api-error-1.8.5.tgz#c49dad22f645227c5edb610bdb9697f1aab721f7"
integrity sha512-Za/tnzsvnqdaSPOUXHyKJ2XI7PDX64kWtURyGiJJZKVEdFOsdKUCPTNEVFZq3zJ2R0G5wc2PZ5gvdTRFgm81zA==
"@webassemblyjs/helper-buffer@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-buffer/-/helper-buffer-1.8.5.tgz#fea93e429863dd5e4338555f42292385a653f204"
integrity sha512-Ri2R8nOS0U6G49Q86goFIPNgjyl6+oE1abW1pS84BuhP1Qcr5JqMwRFT3Ah3ADDDYGEgGs1iyb1DGX+kAi/c/Q==
"@webassemblyjs/helper-code-frame@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-code-frame/-/helper-code-frame-1.8.5.tgz#9a740ff48e3faa3022b1dff54423df9aa293c25e"
integrity sha512-VQAadSubZIhNpH46IR3yWO4kZZjMxN1opDrzePLdVKAZ+DFjkGD/rf4v1jap744uPVU6yjL/smZbRIIJTOUnKQ==
dependencies:
"@webassemblyjs/wast-printer" "1.8.5"
"@webassemblyjs/helper-fsm@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-fsm/-/helper-fsm-1.8.5.tgz#ba0b7d3b3f7e4733da6059c9332275d860702452"
integrity sha512-kRuX/saORcg8se/ft6Q2UbRpZwP4y7YrWsLXPbbmtepKr22i8Z4O3V5QE9DbZK908dh5Xya4Un57SDIKwB9eow==
"@webassemblyjs/helper-module-context@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-module-context/-/helper-module-context-1.8.5.tgz#def4b9927b0101dc8cbbd8d1edb5b7b9c82eb245"
integrity sha512-/O1B236mN7UNEU4t9X7Pj38i4VoU8CcMHyy3l2cV/kIF4U5KoHXDVqcDuOs1ltkac90IM4vZdHc52t1x8Yfs3g==
dependencies:
"@webassemblyjs/ast" "1.8.5"
mamacro "^0.0.3"
"@webassemblyjs/helper-wasm-bytecode@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-wasm-bytecode/-/helper-wasm-bytecode-1.8.5.tgz#537a750eddf5c1e932f3744206551c91c1b93e61"
integrity sha512-Cu4YMYG3Ddl72CbmpjU/wbP6SACcOPVbHN1dI4VJNJVgFwaKf1ppeFJrwydOG3NDHxVGuCfPlLZNyEdIYlQ6QQ==
"@webassemblyjs/helper-wasm-section@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/helper-wasm-section/-/helper-wasm-section-1.8.5.tgz#74ca6a6bcbe19e50a3b6b462847e69503e6bfcbf"
integrity sha512-VV083zwR+VTrIWWtgIUpqfvVdK4ff38loRmrdDBgBT8ADXYsEZ5mPQ4Nde90N3UYatHdYoDIFb7oHzMncI02tA==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-buffer" "1.8.5"
"@webassemblyjs/helper-wasm-bytecode" "1.8.5"
"@webassemblyjs/wasm-gen" "1.8.5"
"@webassemblyjs/ieee754@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/ieee754/-/ieee754-1.8.5.tgz#712329dbef240f36bf57bd2f7b8fb9bf4154421e"
integrity sha512-aaCvQYrvKbY/n6wKHb/ylAJr27GglahUO89CcGXMItrOBqRarUMxWLJgxm9PJNuKULwN5n1csT9bYoMeZOGF3g==
dependencies:
"@xtuc/ieee754" "^1.2.0"
"@webassemblyjs/leb128@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/leb128/-/leb128-1.8.5.tgz#044edeb34ea679f3e04cd4fd9824d5e35767ae10"
integrity sha512-plYUuUwleLIziknvlP8VpTgO4kqNaH57Y3JnNa6DLpu/sGcP6hbVdfdX5aHAV716pQBKrfuU26BJK29qY37J7A==
dependencies:
"@xtuc/long" "4.2.2"
"@webassemblyjs/utf8@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/utf8/-/utf8-1.8.5.tgz#a8bf3b5d8ffe986c7c1e373ccbdc2a0915f0cedc"
integrity sha512-U7zgftmQriw37tfD934UNInokz6yTmn29inT2cAetAsaU9YeVCveWEwhKL1Mg4yS7q//NGdzy79nlXh3bT8Kjw==
"@webassemblyjs/wasm-edit@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-edit/-/wasm-edit-1.8.5.tgz#962da12aa5acc1c131c81c4232991c82ce56e01a"
integrity sha512-A41EMy8MWw5yvqj7MQzkDjU29K7UJq1VrX2vWLzfpRHt3ISftOXqrtojn7nlPsZ9Ijhp5NwuODuycSvfAO/26Q==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-buffer" "1.8.5"
"@webassemblyjs/helper-wasm-bytecode" "1.8.5"
"@webassemblyjs/helper-wasm-section" "1.8.5"
"@webassemblyjs/wasm-gen" "1.8.5"
"@webassemblyjs/wasm-opt" "1.8.5"
"@webassemblyjs/wasm-parser" "1.8.5"
"@webassemblyjs/wast-printer" "1.8.5"
"@webassemblyjs/wasm-gen@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-gen/-/wasm-gen-1.8.5.tgz#54840766c2c1002eb64ed1abe720aded714f98bc"
integrity sha512-BCZBT0LURC0CXDzj5FXSc2FPTsxwp3nWcqXQdOZE4U7h7i8FqtFK5Egia6f9raQLpEKT1VL7zr4r3+QX6zArWg==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-wasm-bytecode" "1.8.5"
"@webassemblyjs/ieee754" "1.8.5"
"@webassemblyjs/leb128" "1.8.5"
"@webassemblyjs/utf8" "1.8.5"
"@webassemblyjs/wasm-opt@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-opt/-/wasm-opt-1.8.5.tgz#b24d9f6ba50394af1349f510afa8ffcb8a63d264"
integrity sha512-HKo2mO/Uh9A6ojzu7cjslGaHaUU14LdLbGEKqTR7PBKwT6LdPtLLh9fPY33rmr5wcOMrsWDbbdCHq4hQUdd37Q==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-buffer" "1.8.5"
"@webassemblyjs/wasm-gen" "1.8.5"
"@webassemblyjs/wasm-parser" "1.8.5"
"@webassemblyjs/wasm-parser@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wasm-parser/-/wasm-parser-1.8.5.tgz#21576f0ec88b91427357b8536383668ef7c66b8d"
integrity sha512-pi0SYE9T6tfcMkthwcgCpL0cM9nRYr6/6fjgDtL6q/ZqKHdMWvxitRi5JcZ7RI4SNJJYnYNaWy5UUrHQy998lw==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-api-error" "1.8.5"
"@webassemblyjs/helper-wasm-bytecode" "1.8.5"
"@webassemblyjs/ieee754" "1.8.5"
"@webassemblyjs/leb128" "1.8.5"
"@webassemblyjs/utf8" "1.8.5"
"@webassemblyjs/wast-parser@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wast-parser/-/wast-parser-1.8.5.tgz#e10eecd542d0e7bd394f6827c49f3df6d4eefb8c"
integrity sha512-daXC1FyKWHF1i11obK086QRlsMsY4+tIOKgBqI1lxAnkp9xe9YMcgOxm9kLe+ttjs5aWV2KKE1TWJCN57/Btsg==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/floating-point-hex-parser" "1.8.5"
"@webassemblyjs/helper-api-error" "1.8.5"
"@webassemblyjs/helper-code-frame" "1.8.5"
"@webassemblyjs/helper-fsm" "1.8.5"
"@xtuc/long" "4.2.2"
"@webassemblyjs/wast-printer@1.8.5":
version "1.8.5"
resolved "https://registry.yarnpkg.com/@webassemblyjs/wast-printer/-/wast-printer-1.8.5.tgz#114bbc481fd10ca0e23b3560fa812748b0bae5bc"
integrity sha512-w0U0pD4EhlnvRyeJzBqaVSJAo9w/ce7/WPogeXLzGkO6hzhr4GnQIZ4W4uUt5b9ooAaXPtnXlj0gzsXEOUNYMg==
dependencies:
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/wast-parser" "1.8.5"
"@xtuc/long" "4.2.2"
"@xtuc/ieee754@^1.2.0":
version "1.2.0"
resolved "https://registry.yarnpkg.com/@xtuc/ieee754/-/ieee754-1.2.0.tgz#eef014a3145ae477a1cbc00cd1e552336dceb790"
integrity sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA==
"@xtuc/long@4.2.2":
version "4.2.2"
resolved "https://registry.yarnpkg.com/@xtuc/long/-/long-4.2.2.tgz#d291c6a4e97989b5c61d9acf396ae4fe133a718d"
integrity sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
abab@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/abab/-/abab-2.0.0.tgz#aba0ab4c5eee2d4c79d3487d85450fb2376ebb0f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-sY5AXXVZv4Y1VACTtR11UJCPHHudgY5i26Qj5TypE6DKlIApbwb5uqhXcJ5UUGbvZNRh7EeIoW+LrJumBsKp7w==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
abbrev@1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/abbrev/-/abbrev-1.1.1.tgz#f8f2c887ad10bf67f634f005b6987fed3179aac8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-nne9/IiQ/hzIhY6pdDnbBtz7DjPTKrY00P/zvPSm5pOFkl6xuGrGnXn/VtTNNfNtAfZ9/1RtehkszU9qcTii0Q==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
accepts@~1.3.4, accepts@~1.3.5, accepts@~1.3.7:
version "1.3.7"
resolved "https://registry.yarnpkg.com/accepts/-/accepts-1.3.7.tgz#531bc726517a3b2b41f850021c6cc15eaab507cd"
integrity sha512-Il80Qs2WjYlJIBNzNkK6KYqlVMTbZLXgHx2oT0pU/fjRHyEp+PEfEPY0R3WCwAGVOtauxh1hOxNgIf5bv7dQpA==
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
mime-types "~2.1.24"
negotiator "0.6.2"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
acorn-globals@^4.1.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "4.3.2"
resolved "https://registry.yarnpkg.com/acorn-globals/-/acorn-globals-4.3.2.tgz#4e2c2313a597fd589720395f6354b41cd5ec8006"
integrity sha512-BbzvZhVtZP+Bs1J1HcwrQe8ycfO0wStkSGxuul3He3GkHOIZ6eTqOkPuw9IP1X3+IkOo4wiJmwkobzXYz4wewQ==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
acorn "^6.0.1"
acorn-walk "^6.0.1"
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
acorn-jsx@^5.0.0:
version "5.0.1"
resolved "https://registry.yarnpkg.com/acorn-jsx/-/acorn-jsx-5.0.1.tgz#32a064fd925429216a09b141102bfdd185fae40e"
integrity sha512-HJ7CfNHrfJLlNTzIEUTj43LNWGkqpRLxm3YjAlcD0ACydk9XynzYsCBHxut+iqt+1aBXkx9UP/w/ZqMr13XIzg==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
acorn-walk@^6.0.1:
version "6.2.0"
resolved "https://registry.yarnpkg.com/acorn-walk/-/acorn-walk-6.2.0.tgz#123cb8f3b84c2171f1f7fb252615b1c78a6b1a8c"
integrity sha512-7evsyfH1cLOCdAzZAd43Cic04yKydNx0cF+7tiA19p1XnLLPU4dpCQOqpjqwokFe//vS0QqfqqjCS2JkiIs0cA==
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
acorn@^5.5.3:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "5.7.3"
resolved "https://registry.yarnpkg.com/acorn/-/acorn-5.7.3.tgz#67aa231bf8812974b85235a96771eb6bd07ea279"
integrity sha512-T/zvzYRfbVojPWahDsE5evJdHb3oJoQfFbsrKM7w5Zcs++Tr257tia3BmMP8XYVjp1S9RZXQMh7gao96BlqZOw==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
acorn@^6.0.1, acorn@^6.0.7, acorn@^6.2.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "6.2.0"
resolved "https://registry.yarnpkg.com/acorn/-/acorn-6.2.0.tgz#67f0da2fc339d6cfb5d6fb244fd449f33cd8bbe3"
integrity sha512-8oe72N3WPMjA+2zVG71Ia0nXZ8DpQH+QyyHO+p06jT8eg8FGG3FbcUIi8KziHlAfheJQZeoqbvq1mQSQHXKYLw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
address@1.0.3:
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
version "1.0.3"
resolved "https://registry.yarnpkg.com/address/-/address-1.0.3.tgz#b5f50631f8d6cec8bd20c963963afb55e06cbce9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-z55ocwKBRLryBs394Sm3ushTtBeg6VAeuku7utSoSnsJKvKcnXFIyC6vh27n3rXyxSgkJBBCAvyOn7gSUcTYjg==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
address@^1.0.1:
version "1.1.0"
resolved "https://registry.yarnpkg.com/address/-/address-1.1.0.tgz#ef8e047847fcd2c5b6f50c16965f924fd99fe709"
integrity sha512-4diPfzWbLEIElVG4AnqP+00SULlPzNuyJFNnmMrLgyaxG6tZXJ1sn7mjBu4fHrJE+Yp/jgylOweJn2xsLMFggQ==
airbnb-prop-types@^2.13.2:
version "2.13.2"
resolved "https://registry.yarnpkg.com/airbnb-prop-types/-/airbnb-prop-types-2.13.2.tgz#43147a5062dd2a4a5600e748a47b64004cc5f7fc"
integrity sha512-2FN6DlHr6JCSxPPi25EnqGaXC4OC3/B3k1lCd6MMYrZ51/Gf/1qDfaR+JElzWa+Tl7cY2aYOlsYJGFeQyVHIeQ==
dependencies:
array.prototype.find "^2.0.4"
function.prototype.name "^1.1.0"
has "^1.0.3"
is-regex "^1.0.4"
object-is "^1.0.1"
object.assign "^4.1.0"
object.entries "^1.1.0"
prop-types "^15.7.2"
prop-types-exact "^1.2.0"
react-is "^16.8.6"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
ajv-errors@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/ajv-errors/-/ajv-errors-1.0.1.tgz#f35986aceb91afadec4102fbd85014950cefa64d"
integrity sha512-DCRfO/4nQ+89p/RK43i8Ezd41EqdGIU4ld7nGF8OQ14oc/we5rEntLCUa7+jrn3nn83BosfwZA0wb4pon2o8iQ==
Tweak package.json - Remove obsolete eslint react app config - Pin webpack major version Test plan: yarn && yarn test
2019-07-05 18:31:37 +00:00
ajv-keywords@^3.1.0:
version "3.4.0"
resolved "https://registry.yarnpkg.com/ajv-keywords/-/ajv-keywords-3.4.0.tgz#4b831e7b531415a7cc518cd404e73f6193c6349d"
integrity sha512-aUjdRFISbuFOl0EIZc+9e4FfZp0bDZgAdOOf30bJmw8VM9v84SHyVyxDfbWxpGYbdZD/9XoKxfHVNmxPkhwyGw==
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
Tweak package.json - Remove obsolete eslint react app config - Pin webpack major version Test plan: yarn && yarn test
2019-07-05 18:31:37 +00:00
ajv@^6.1.0, ajv@^6.10.0, ajv@^6.5.5, ajv@^6.9.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "6.10.0"
resolved "https://registry.yarnpkg.com/ajv/-/ajv-6.10.0.tgz#90d0d54439da587cd7e843bfb7045f50bd22bdf1"
integrity sha512-nffhOpkymDECQyR0mnsUtoCE8RlX38G0rYP+wgLWFyZuUyuuojSSvi/+euOiQBIn63whYwYVIIH1TvE3tu4OEg==
dependencies:
fast-deep-equal "^2.0.1"
fast-json-stable-stringify "^2.0.0"
json-schema-traverse "^0.4.1"
uri-js "^4.2.2"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
ansi-colors@^3.0.0:
version "3.2.4"
resolved "https://registry.yarnpkg.com/ansi-colors/-/ansi-colors-3.2.4.tgz#e3a3da4bfbae6c86a9c285625de124a234026fbf"
integrity sha512-hHUXGagefjN2iRrID63xckIvotOXOojhQKWIPUZ4mNUZ9nLZW+7FMNoE1lOkEhNWYsx/7ysGIuJYCiMAA9FnrA==
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
ansi-escapes@^3.0.0, ansi-escapes@^3.2.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.2.0"
resolved "https://registry.yarnpkg.com/ansi-escapes/-/ansi-escapes-3.2.0.tgz#8780b98ff9dbf5638152d1f1fe5c1d7b4442976b"
integrity sha512-cBhpre4ma+U0T1oM5fXg7Dy1Jw7zzwv7lt/GoCpr+hDQJoYnKVPLL4dCvSEFMmQurOQvSrwT7SL/DAlhBI97RQ==
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
ansi-html@0.0.7:
version "0.0.7"
resolved "https://registry.yarnpkg.com/ansi-html/-/ansi-html-0.0.7.tgz#813584021962a9e9e6fd039f940d12f56ca7859e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-gTWEAhliqenm/QOflA0S9WynhZ4=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
ansi-regex@^2.0.0:
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
version "2.1.1"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-2.1.1.tgz#c3b33ab5ee360d86e0e628f0468ae7ef27d654df"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-w7M6te42DYbg5ijwRorn7yfWVN8=
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
ansi-regex@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-3.0.0.tgz#ed0317c322064f79466c02966bddb605ab37d998"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-7QMXwyIGT3lGbAKWa922Bas32Zg=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
ansi-regex@^4.0.0, ansi-regex@^4.1.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-4.1.0.tgz#8b9f8f08cf1acb843756a839ca8c7e3168c51997"
integrity sha512-1apePfXM1UOSqw0o9IiFAovVz9M5S1Dg+4TrDwfMewQ6p/rmMueb7tWZjQ1rx4Loy1ArBggoqGpfqqdI4rondg==
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
ansi-styles@^2.2.1:
version "2.2.1"
resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-2.2.1.tgz#b432dd3358b634cf75e1e4664368240533c1ddbe"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-tDLdM1i2NM914eRmQ2gkBTPB3b4=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
ansi-styles@^3.2.0, ansi-styles@^3.2.1:
Minimal toy oclif integration (#214) This commit adds [oclif] as a command-line framework. It is successfully integrated with webpack. [oclif]: https://github.com/oclif/oclif Usage: `yarn backend` to build the cli. `node bin/sourcecred.js` to launch the CLI and see usage `node bin/sourcecred.js example` for one example command `node bin/sourcecred.js goodbye` for another example command
2018-05-05 02:28:37 +00:00
version "3.2.1"
resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-3.2.1.tgz#41fbb20243e50b12be0f04b8dedbf07520ce841d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==
Minimal toy oclif integration (#214) This commit adds [oclif] as a command-line framework. It is successfully integrated with webpack. [oclif]: https://github.com/oclif/oclif Usage: `yarn backend` to build the cli. `node bin/sourcecred.js` to launch the CLI and see usage `node bin/sourcecred.js example` for one example command `node bin/sourcecred.js goodbye` for another example command
2018-05-05 02:28:37 +00:00
dependencies:
color-convert "^1.9.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
anymatch@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/anymatch/-/anymatch-2.0.0.tgz#bcb24b4f37934d9aa7ac17b4adaf89e7c76ef2eb"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-5teOsQWABXHHBFP9y3skS5P3d/WfWXpv3FUpy+LorMrNYaT9pI4oLMQX7jzQ2KklNpGpWHzdCXTDT2Y3XGlZBw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
micromatch "^3.1.4"
normalize-path "^2.1.1"
Add style support to the artifacts app Test Plan: Note that the header, when rendered, is magenta. wchargin-branch: stylish-artifacts
2018-03-19 22:31:08 +00:00
aphrodite@^2.1.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.3.1"
resolved "https://registry.yarnpkg.com/aphrodite/-/aphrodite-2.3.1.tgz#376b9964c8742218fd10b8b82786f9d22e650e41"
integrity sha512-hwRxpYarrHLRti62RlWplK3A1bDkh4dw5jjDh4Xvra6z45B5yx9Rqsiaw3duELCI/FLOYxlxVe1bysRpIw5X1Q==
Add style support to the artifacts app Test Plan: Note that the header, when rendered, is magenta. wchargin-branch: stylish-artifacts
2018-03-19 22:31:08 +00:00
dependencies:
asap "^2.0.3"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
inline-style-prefixer "^5.0.4"
Add style support to the artifacts app Test Plan: Note that the header, when rendered, is magenta. wchargin-branch: stylish-artifacts
2018-03-19 22:31:08 +00:00
string-hash "^1.1.3"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
aproba@^1.0.3, aproba@^1.1.1:
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
version "1.2.0"
resolved "https://registry.yarnpkg.com/aproba/-/aproba-1.2.0.tgz#6802e6264efd18c790a1b0d517f0f2627bf2c94a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-Y9J6ZjXtoYh8RnXVCMOU/ttDmk1aBjunq9vO0ta5x85WDQiQfUF9sIPBITdbiiIVcBo03Hi3jMxigBtsddlXRw==
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
are-we-there-yet@~1.1.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.5"
resolved "https://registry.yarnpkg.com/are-we-there-yet/-/are-we-there-yet-1.1.5.tgz#4b35c2944f062a8bfcda66410760350fe9ddfc21"
integrity sha512-5hYdAkZlcG8tOLujVDTgCT+uPX0VnpAH28gWsLfzpXYm7wP6mp5Q/gYyR7YQ0cKVJcXJnl3j2kpBan13PtQf6w==
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:
delegates "^1.0.0"
readable-stream "^2.0.6"
argparse@^1.0.7:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.10"
resolved "https://registry.yarnpkg.com/argparse/-/argparse-1.0.10.tgz#bcd6791ea5ae09725e17e5ad988134cd40b3d911"
integrity sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==
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:
sprintf-js "~1.0.2"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
aria-query@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/aria-query/-/aria-query-3.0.0.tgz#65b3fcc1ca1155a8c9ae64d6eee297f15d5133cc"
integrity sha1-ZbP8wcoRVajJrmTW7uKX8V1RM8w=
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:
ast-types-flow "0.0.7"
commander "^2.11.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
arr-diff@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/arr-diff/-/arr-diff-4.0.0.tgz#d6461074febfec71e7e15235761a329a5dc7c520"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-1kYQdP6/7HHn4VI1dhoyml3HxSA=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
arr-flatten@^1.1.0:
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
version "1.1.0"
resolved "https://registry.yarnpkg.com/arr-flatten/-/arr-flatten-1.1.0.tgz#36048bbff4e7b47e136644316c99669ea5ae91f1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-L3hKV5R/p5o81R7O02IGnwpDmkp6E982XhtbuwSe3O4qOtMMMtodicASA1Cny2U+aCXcNpml+m4dPsvsJ3jatg==
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
arr-union@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/arr-union/-/arr-union-3.1.0.tgz#e39b09aea9def866a8f206e288af63919bae39c4"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-45sJrqne+Gao8gbiiK9jkZuuOcQ=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
array-equal@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/array-equal/-/array-equal-1.0.0.tgz#8c2a5ef2472fd9ea742b04c77a75093ba2757c93"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-jCpe8kcv2ep0KwTHenUJO6J1fJM=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
array-filter@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/array-filter/-/array-filter-1.0.0.tgz#baf79e62e6ef4c2a4c0b831232daffec251f9d83"
integrity sha1-uveeYubvTCpMC4MSMtr/7CUfnYM=
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
array-filter@~0.0.0:
version "0.0.1"
resolved "https://registry.yarnpkg.com/array-filter/-/array-filter-0.0.1.tgz#7da8cf2e26628ed732803581fd21f67cacd2eeec"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-fajPLiZijtcygDWB/SH2fKzS7uw=
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
array-flatten@1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/array-flatten/-/array-flatten-1.1.1.tgz#9a5f699051b1e7073328f2a008968b64ea2955d2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-ml9pkFGx5wczKPKgCJaLZOopVdI=
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
array-flatten@^2.1.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.1.2"
resolved "https://registry.yarnpkg.com/array-flatten/-/array-flatten-2.1.2.tgz#24ef80a28c1a893617e2149b0c6d0d788293b099"
integrity sha512-hNfzcOV8W4NdualtqBFPyVO+54DSJuZGY9qT4pRroB6S9e3iiido2ISIC5h9R2sPJ8H3FHCIiEnsv1lPXO3KtQ==
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
array-includes@^3.0.3:
version "3.0.3"
resolved "https://registry.yarnpkg.com/array-includes/-/array-includes-3.0.3.tgz#184b48f62d92d7452bb31b323165c7f8bd02266d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-GEtI9i2S10UrsxsyMWXH+L0CJm0=
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:
define-properties "^1.1.2"
es-abstract "^1.7.0"
array-map@~0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/array-map/-/array-map-0.0.0.tgz#88a2bab73d1cf7bcd5c1b118a003f66f665fa662"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-iKK6tz0c97zVwbEYoAP2b2ZfpmI=
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
array-reduce@~0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/array-reduce/-/array-reduce-0.0.0.tgz#173899d3ffd1c7d9383e4479525dbe278cab5f2b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-FziZ0//Rx9k4PkR5Ul2+J4yrXys=
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
array-union@^1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/array-union/-/array-union-1.0.2.tgz#9a34410e4f4e3da23dea375be5be70f24778ec39"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-mjRBDk9OPaI96jdb5b5w8kd47Dk=
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:
array-uniq "^1.0.1"
array-uniq@^1.0.1:
version "1.0.3"
resolved "https://registry.yarnpkg.com/array-uniq/-/array-uniq-1.0.3.tgz#af6ac877a25cc7f74e058894753858dfdb24fdb6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-r2rId6Jcx/dOBYiUdThY39sk/bY=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
array-unique@^0.3.2:
version "0.3.2"
resolved "https://registry.yarnpkg.com/array-unique/-/array-unique-0.3.2.tgz#a894b75d4bc4f6cd679ef3244a9fd8f46ae2d428"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-qJS3XUvE9s1nnvMkSp/Y9Gri1Cg=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
array.prototype.find@^2.0.4:
version "2.1.0"
resolved "https://registry.yarnpkg.com/array.prototype.find/-/array.prototype.find-2.1.0.tgz#630f2eaf70a39e608ac3573e45cf8ccd0ede9ad7"
integrity sha512-Wn41+K1yuO5p7wRZDl7890c3xvv5UBrfVXTVIe28rSQb6LS0fZMDrQB6PAcxQFRFy6vJTLDc3A2+3CjQdzVKRg==
dependencies:
define-properties "^1.1.3"
es-abstract "^1.13.0"
array.prototype.flat@^1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/array.prototype.flat/-/array.prototype.flat-1.2.1.tgz#812db8f02cad24d3fab65dd67eabe3b8903494a4"
integrity sha512-rVqIs330nLJvfC7JqYvEWwqVr5QjYF1ib02i3YJtR/fICO6527Tjpc/e4Mvmxh3GIePPreRXMdaGyC99YphWEw==
dependencies:
define-properties "^1.1.2"
es-abstract "^1.10.0"
function-bind "^1.1.1"
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
asap@^2.0.3, asap@~2.0.3, asap@~2.0.6:
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
version "2.0.6"
resolved "https://registry.yarnpkg.com/asap/-/asap-2.0.6.tgz#e50347611d7e690943208bbdafebcbc2fb866d46"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-5QNHYR1+aQlDIIu9r+vLwvuGbUY=
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
asn1.js@^4.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "4.10.1"
resolved "https://registry.yarnpkg.com/asn1.js/-/asn1.js-4.10.1.tgz#b9c2bf5805f1e64aadeed6df3a2bfafb5a73f5a0"
integrity sha512-p32cOF5q0Zqs9uBiONKYLm6BClCoBCM5O9JfeUSlnQLBTxYdTK+pW+nXflm8UkKd2UYlEbYz5qEi0JuZR9ckSw==
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:
bn.js "^4.0.0"
inherits "^2.0.1"
minimalistic-assert "^1.0.0"
asn1@~0.2.3:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "0.2.4"
resolved "https://registry.yarnpkg.com/asn1/-/asn1-0.2.4.tgz#8d2475dfab553bb33e77b54e59e880bb8ce23136"
integrity sha512-jxwzQpLQjSmWXgwaCZE9Nz+glAG01yF1QnWgbhGwHI5A6FRIEY6IVqtHhIepHqI7/kyEyQEagBC5mBEFlIYvdg==
dependencies:
safer-buffer "~2.1.0"
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
assert-plus@1.0.0, assert-plus@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/assert-plus/-/assert-plus-1.0.0.tgz#f12e0f3c5d77b0b1cdd9146942e4e96c1e4dd525"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-8S4PPF13sLHN2RRpQuTpbB5N1SU=
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
assert@^1.1.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.5.0"
resolved "https://registry.yarnpkg.com/assert/-/assert-1.5.0.tgz#55c109aaf6e0aefdb3dc4b71240c70bf574b18eb"
integrity sha512-EDsgawzwoun2CZkCgtxJbv392v4nbk9XDD06zI+kQYoBM/3RBWLlEyJARDOmhAAosBjWACEkKL6S+lIZtcAubA==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
object-assign "^4.1.1"
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
util "0.10.3"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
assign-symbols@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/assign-symbols/-/assign-symbols-1.0.0.tgz#59667f41fadd4f20ccbc2bb96b8d4f7f78ec0367"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-WWZ/QfrdTyDMvCu5a41Pf3jsA2c=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
ast-types-flow@0.0.7, ast-types-flow@^0.0.7:
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
version "0.0.7"
resolved "https://registry.yarnpkg.com/ast-types-flow/-/ast-types-flow-0.0.7.tgz#f70b735c6bca1a5c9c22d982c3e39e7feba3bdad"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-9wtzXGvKGlycItmCw+Oef+ujva0=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
astral-regex@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/astral-regex/-/astral-regex-1.0.0.tgz#6c8c3fb827dd43ee3918f27b82782ab7658a6fd9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-+Ryf6g3BKoRc7jfp7ad8tM4TtMiaWvbF/1/sQcZPkkS7ag3D5nMBCe2UfOTONtAkaG0tO0ij3C5Lwmf1EiyjHg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
async-each@^1.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/async-each/-/async-each-1.0.3.tgz#b727dbf87d7651602f06f4d4ac387f47d91b0cbf"
integrity sha512-z/WhQ5FPySLdvREByI2vZiTWwCnF0moMJ1hK9YQwDTHKh6I7/uSckMetoRGb5UBZPC1z0jlw+n/XCgjeH7y1AQ==
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
async-limiter@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/async-limiter/-/async-limiter-1.0.0.tgz#78faed8c3d074ab81f22b4e985d79e8738f720f8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-jp/uFnooOiO+L211eZOoSyzpOITMXx1rBITauYykG3BRYPu8h0UcxsPNB04RR5vo4Tyz3+ay17tR6JVf9qzYWg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
async@^1.5.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
version "1.5.2"
resolved "https://registry.yarnpkg.com/async/-/async-1.5.2.tgz#ec6a61ae56480c0c3cb241c95618e20892f9672a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-7GphrlZIDAw8skHJVhjiCJL5Zyo=
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
asynckit@^0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/asynckit/-/asynckit-0.4.0.tgz#c79ed97f7f34cb8f2ba1bc9790bcc366474b4b79"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-x57Zf380y48robyXkLzDZkdLS3k=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
atob@^2.1.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.1.2"
resolved "https://registry.yarnpkg.com/atob/-/atob-2.1.2.tgz#6d9517eb9e030d2436666651e86bd9f6f13533c9"
integrity sha512-Wm6ukoaOGJi/73p/cl2GvLjTI5JM1k/O14isD73YML8StrH/7/lRFgmg8nICZgD3bZZvjwCGxtMOD3wWNAu8cg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
aws-sign2@~0.7.0:
version "0.7.0"
resolved "https://registry.yarnpkg.com/aws-sign2/-/aws-sign2-0.7.0.tgz#b46e890934a9591f2d2f6f86d7e6a9f1b3fe76a8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-tG6JCTSpWR8tL2+G1+ap8bP+dqg=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
aws4@^1.8.0:
version "1.8.0"
resolved "https://registry.yarnpkg.com/aws4/-/aws4-1.8.0.tgz#f0e003d9ca9e7f59c7a508945d7b2ef9a04a542f"
integrity sha512-ReZxvNHIOv88FlT7rxcXIIC0fPt4KZqZbOlivyWtXLt8ESx84zd3kMC6iK5jVeS2qt+g7ftS7ye4fi06X5rtRQ==
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
axobject-query@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/axobject-query/-/axobject-query-2.0.2.tgz#ea187abe5b9002b377f925d8bf7d1c561adf38f9"
integrity sha512-MCeek8ZH7hKyO1rWUbKNQBbl4l2eY0ntk7OGi+q0RlafrCnfPxC06WZA+uebCfmYp4mNU9jRBP1AhGyf8+W3ww==
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:
ast-types-flow "0.0.7"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
babel-code-frame@6.26.0:
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
version "6.26.0"
resolved "https://registry.yarnpkg.com/babel-code-frame/-/babel-code-frame-6.26.0.tgz#63fd43f7dc1e3bb7ce35947db8fe369a3f58c74b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Y/1D99weO7fONZR9uP42mj9Yx0s=
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:
chalk "^1.1.3"
esutils "^2.0.2"
js-tokens "^3.0.2"
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-eslint@^10.0.2:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
version "10.0.2"
resolved "https://registry.yarnpkg.com/babel-eslint/-/babel-eslint-10.0.2.tgz#182d5ac204579ff0881684b040560fdcc1558456"
integrity sha512-UdsurWPtgiPgpJ06ryUnuaSXC2s0WoSZnQmEpbAH65XZSdwowgN5MvyP7e88nW07FYXv72erVtpBkxyDVKhH1Q==
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:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
"@babel/code-frame" "^7.0.0"
"@babel/parser" "^7.0.0"
"@babel/traverse" "^7.0.0"
"@babel/types" "^7.0.0"
eslint-scope "3.7.1"
eslint-visitor-keys "^1.0.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
babel-jest@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/babel-jest/-/babel-jest-24.8.0.tgz#5c15ff2b28e20b0f45df43fe6b7f2aae93dba589"
integrity sha512-+5/kaZt4I9efoXzPlZASyK/lN9qdRKmmUav9smVc0ruPQD7IsfucQ87gpOE8mn2jbDuS6M/YOW6n3v9ZoIfgnw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/transform" "^24.8.0"
"@jest/types" "^24.8.0"
"@types/babel__core" "^7.1.0"
babel-plugin-istanbul "^5.1.0"
babel-preset-jest "^24.6.0"
chalk "^2.4.2"
slash "^2.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
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:
version "8.0.6"
resolved "https://registry.yarnpkg.com/babel-loader/-/babel-loader-8.0.6.tgz#e33bdb6f362b03f4bb141a0c21ab87c501b70dfb"
integrity sha512-4BmWKtBOBm13uoUwd08UwjZlaw3O9GWf456R9j+5YykFZ6LUIjIKLc0zEZf+hauxPOJs96C8k6FvYD09vWzhYw==
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:
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
find-cache-dir "^2.0.0"
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
loader-utils "^1.0.2"
mkdirp "^0.5.1"
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
pify "^4.0.1"
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
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-plugin-dynamic-import-node@^2.3.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/babel-plugin-dynamic-import-node/-/babel-plugin-dynamic-import-node-2.3.0.tgz#f00f507bdaa3c3e3ff6e7e5e98d90a7acab96f7f"
integrity sha512-o6qFkpeQEBxcqt0XYlWzAVxNCSCZdUgcR8IRlhD/8DylxjjO4foPcvTW0GGKa/cVt3rvxZ7o5ippJ+/0nvLhlQ==
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:
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
object.assign "^4.1.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
babel-plugin-istanbul@^5.1.0:
version "5.1.4"
resolved "https://registry.yarnpkg.com/babel-plugin-istanbul/-/babel-plugin-istanbul-5.1.4.tgz#841d16b9a58eeb407a0ddce622ba02fe87a752ba"
integrity sha512-dySz4VJMH+dpndj0wjJ8JPs/7i1TdSPb1nRrn56/92pKOF9VKC1FMFJmMXjzlGGusnCAqujP6PBCiKq0sVA+YQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
find-up "^3.0.0"
istanbul-lib-instrument "^3.3.0"
test-exclude "^5.2.3"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
babel-plugin-jest-hoist@^24.6.0:
version "24.6.0"
resolved "https://registry.yarnpkg.com/babel-plugin-jest-hoist/-/babel-plugin-jest-hoist-24.6.0.tgz#f7f7f7ad150ee96d7a5e8e2c5da8319579e78019"
integrity sha512-3pKNH6hMt9SbOv0F3WVmy5CWQ4uogS3k0GY5XLyQHJ9EGpAT9XWkFd2ZiXXtkwFHdAHa5j7w7kfxSP5lAIwu7w==
dependencies:
"@types/babel__traverse" "^7.0.6"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
babel-preset-jest@^24.6.0:
version "24.6.0"
resolved "https://registry.yarnpkg.com/babel-preset-jest/-/babel-preset-jest-24.6.0.tgz#66f06136eefce87797539c0d63f1769cc3915984"
integrity sha512-pdZqLEdmy1ZK5kyRUfvBb2IfTPb2BUvIJczlPspS8fWmBQslNNDBqVfh7BW5leOVJMDZKzjD8XEyABTk6gQ5yw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/plugin-syntax-object-rest-spread" "^7.0.0"
babel-plugin-jest-hoist "^24.6.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
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
bail@^1.0.0:
version "1.0.4"
resolved "https://registry.yarnpkg.com/bail/-/bail-1.0.4.tgz#7181b66d508aa3055d3f6c13f0a0c720641dde9b"
integrity sha512-S8vuDB4w6YpRhICUDET3guPlQpaJl7od94tpZ0Fvnyp+MKW/HyDTcRDck+29C9g+d/qQHnddRH3+94kZdrW0Ww==
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
balanced-match@^0.4.2:
version "0.4.2"
resolved "https://registry.yarnpkg.com/balanced-match/-/balanced-match-0.4.2.tgz#cb3f3e3c732dc0f01ee70b403f302e61d7709838"
integrity sha1-yz8+PHMtwPAe5wtAPzAuYddwmDg=
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
balanced-match@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.0.tgz#89b4d199ab2bee49de164ea02b89ce462d71b767"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-ibTRmasr7kneFk6gK4nORi1xt2c=
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
Add `core/project` and `core/project_io` This creates a new `Project` type which will replace `RepoId` as the index type for saving and loading data. The basic data type is added to `project.js`. Rather than having a `RepoIdRegistry`, I intend to infer the registry at build time by scanning for available projects saved in the sourcecred directory. I've added the `project_io` module for this task. It has methods for setting up a project subdirectory, and loading the `Project` info from that subdirectory. To ensure that projects ids can be encoded even if they have symbols like `/` and `@`, we base64 encode them. To ensure that project ids can be retrieved at build time, the `getProjectIds` method is factored out into its own plain ECMAScript module. For all non-build time needs, it is re-exported from `project_io`. Test plan: Unit tests added; run `yarn test`.
2019-07-18 17:45:49 +00:00
base-64@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/base-64/-/base-64-0.1.0.tgz#780a99c84e7d600260361511c4877613bf24f6bb"
integrity sha1-eAqZyE59YAJgNhURxId2E78k9rs=
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
base64-js@^1.0.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/base64-js/-/base64-js-1.3.0.tgz#cab1e6118f051095e58b5281aea8c1cd22bfc0e3"
integrity sha512-ccav/yGvoa80BQDljCxsmmQ3Xvx60/UpBIij5QN21W3wBi/hhIC9OoO+KLpu9IJTS9j4DRVJ3aDDF9cMSoa2lw==
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
base@^0.11.1:
version "0.11.2"
resolved "https://registry.yarnpkg.com/base/-/base-0.11.2.tgz#7bde5ced145b6d551a90db87f83c558b4eb48a8f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-5T6P4xPgpp0YDFvSWwEZ4NoE3aM4QBQXDzmVbraCkFj8zHM+mba8SyqB5DbZWyR7mYHo6Y7BdQo3MoA4m0TeQg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
cache-base "^1.0.1"
class-utils "^0.3.5"
component-emitter "^1.2.1"
define-property "^1.0.0"
isobject "^3.0.1"
mixin-deep "^1.2.0"
pascalcase "^0.1.1"
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
batch@0.6.1:
version "0.6.1"
resolved "https://registry.yarnpkg.com/batch/-/batch-0.6.1.tgz#dc34314f4e679318093fc760272525f94bf25c16"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-3DQxT05nkxgJP8dgJyUl+UvyXBY=
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
bcrypt-pbkdf@^1.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/bcrypt-pbkdf/-/bcrypt-pbkdf-1.0.2.tgz#a4301d389b6a43f9b67ff3ca11a3f6637e360e9e"
integrity sha1-pDAdOJtqQ/m2f/PKEaP2Y342Dp4=
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:
tweetnacl "^0.14.3"
Update better-sqlite3 to v5 When we took a dep on better-sqlite3 in #836, we used a fork, because better-sqlite3 did not yet support private in-memory databases via the `:memory:` filepath. As of better-sqlite3 v5, this has been added to mainline, so we no longer need the fork. The v4->v5 transition involves some breaking changes. The only ones that affected us were two field renames, from `lastUpdateROWID` to `lastUpdateRowid`, and `returnsData` to `reader`. Test plan: After updating the field accesses, `yarn test --full` passes. For added safety, I also blew away cache, loaded a nontrivial repository, and verified that the full cred workflow still works. cc @wchargin
2019-07-04 16:48:34 +00:00
better-sqlite3@^5.4.0:
version "5.4.0"
resolved "https://registry.yarnpkg.com/better-sqlite3/-/better-sqlite3-5.4.0.tgz#88c4894f6c0484dc0a89a9ba12268976cd26b1da"
integrity sha512-Uj1ZYOcq1GtFyFgJgqMVDoDLTy1B1pM9+bULnlX8szRX4cPjE/7JbKxCzQGhYlZlLkHQvtXXhCZ3skqsQ2byMA==
deps: add `better-sqlite3` (#836) Summary: I selected this over the alternatives, `sqlite` and `sqlite3`, primarily because its README explicitly acknowledges that using asynchronous APIs for CPU-bound or serialized work units are worse than useless. To me, this is a sign that the maintainer has his head on straight. The many-fold performance increase over `sqlite` and `sqlite3` is nice to have, too. For now, we use my fork of the project, which includes a critical patch to support private in-memory databases via SQLite’s standard `:memory:` filepath. When this patch is merged upstream, we can move back to mainline. Test Plan: The following session demonstrates the basic API and validates that the install has completed successfully: ```js const Database = require("better-sqlite3"); const db = new Database("/tmp/irrelevant", {memory: true}); db.prepare("CREATE TABLE pythagorean_triples (x, y, z)").run(); const insert = db.prepare("INSERT INTO pythagorean_triples VALUES (?, ?, ?)"); const get = db.prepare( "SELECT rowid, x * x + y * y AS xxyy, z * z AS zz FROM pythagorean_triples" ); function print(x) { console.log(JSON.stringify(x)); } print(insert.run(3, 4, 5)); print(get.all()); print(insert.run(5, 12, 13)); print(get.all()); db.prepare("DELETE FROM pythagorean_triples").run(); print(get.all()); ``` It prints: ```js {"changes":1,"lastInsertROWID":1} [{"rowid":1,"xxyy":25,"zz":25}] {"changes":1,"lastInsertROWID":2} [{"rowid":1,"xxyy":25,"zz":25},{"rowid":2,"xxyy":169,"zz":169}] [] ``` wchargin-branch: dep-better-sqlite3
2018-09-14 01:20:10 +00:00
dependencies:
Update better-sqlite3 to v5 When we took a dep on better-sqlite3 in #836, we used a fork, because better-sqlite3 did not yet support private in-memory databases via the `:memory:` filepath. As of better-sqlite3 v5, this has been added to mainline, so we no longer need the fork. The v4->v5 transition involves some breaking changes. The only ones that affected us were two field renames, from `lastUpdateROWID` to `lastUpdateRowid`, and `returnsData` to `reader`. Test plan: After updating the field accesses, `yarn test --full` passes. For added safety, I also blew away cache, loaded a nontrivial repository, and verified that the full cred workflow still works. cc @wchargin
2019-07-04 16:48:34 +00:00
integer "^2.1.0"
tar "^4.4.6"
deps: add `better-sqlite3` (#836) Summary: I selected this over the alternatives, `sqlite` and `sqlite3`, primarily because its README explicitly acknowledges that using asynchronous APIs for CPU-bound or serialized work units are worse than useless. To me, this is a sign that the maintainer has his head on straight. The many-fold performance increase over `sqlite` and `sqlite3` is nice to have, too. For now, we use my fork of the project, which includes a critical patch to support private in-memory databases via SQLite’s standard `:memory:` filepath. When this patch is merged upstream, we can move back to mainline. Test Plan: The following session demonstrates the basic API and validates that the install has completed successfully: ```js const Database = require("better-sqlite3"); const db = new Database("/tmp/irrelevant", {memory: true}); db.prepare("CREATE TABLE pythagorean_triples (x, y, z)").run(); const insert = db.prepare("INSERT INTO pythagorean_triples VALUES (?, ?, ?)"); const get = db.prepare( "SELECT rowid, x * x + y * y AS xxyy, z * z AS zz FROM pythagorean_triples" ); function print(x) { console.log(JSON.stringify(x)); } print(insert.run(3, 4, 5)); print(get.all()); print(insert.run(5, 12, 13)); print(get.all()); db.prepare("DELETE FROM pythagorean_triples").run(); print(get.all()); ``` It prints: ```js {"changes":1,"lastInsertROWID":1} [{"rowid":1,"xxyy":25,"zz":25}] {"changes":1,"lastInsertROWID":2} [{"rowid":1,"xxyy":25,"zz":25},{"rowid":2,"xxyy":169,"zz":169}] [] ``` wchargin-branch: dep-better-sqlite3
2018-09-14 01:20:10 +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
big.js@^3.1.3:
version "3.2.0"
resolved "https://registry.yarnpkg.com/big.js/-/big.js-3.2.0.tgz#a5fc298b81b9e0dca2e458824784b65c52ba588e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-+hN/Zh2D08Mx65pZ/4g5bsmNiZUuChDiQfTUQ7qJr4/kuopCr88xZsAXv6mBoZEsUI4OuGHlX59qE94K2mMW8Q==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
big.js@^5.2.2:
version "5.2.2"
resolved "https://registry.yarnpkg.com/big.js/-/big.js-5.2.2.tgz#65f0af382f578bcdc742bd9c281e9cb2d7768328"
integrity sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
binary-extensions@^1.0.0:
version "1.13.1"
resolved "https://registry.yarnpkg.com/binary-extensions/-/binary-extensions-1.13.1.tgz#598afe54755b2868a5330d2aff9d4ebb53209b65"
integrity sha512-Un7MIEDdUC5gNpcGDV97op1Ywk748MpHcFTHoYs6qnj1Z3j7I53VG3nwZhKzoBZmbdRNnb6WRdFlwl7tSDuZGw==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
bluebird@^3.0.5, bluebird@^3.5.5:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.5.5"
resolved "https://registry.yarnpkg.com/bluebird/-/bluebird-3.5.5.tgz#a8d0afd73251effbbd5fe384a77d73003c17a71f"
integrity sha512-5am6HnnfN+urzt4yfg7IgTbotDjIT/u8AJpEt0sIU9FtXfVeezXAPKswrG+xKUCOYAINpSdgZVDU6QFh+cuH3w==
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
bn.js@^4.0.0, bn.js@^4.1.0, bn.js@^4.1.1, bn.js@^4.4.0:
version "4.11.8"
resolved "https://registry.yarnpkg.com/bn.js/-/bn.js-4.11.8.tgz#2cde09eb5ee341f484746bb0309b3253b1b1442f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-ItfYfPLkWHUjckQCk8xC+LwxgK8NYcXywGigJgSwOP8Y2iyWT4f2vsZnoOXTTbo+o5yXmIUJ4gn5538SO5S3gA==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
body-parser@1.19.0:
version "1.19.0"
resolved "https://registry.yarnpkg.com/body-parser/-/body-parser-1.19.0.tgz#96b2709e57c9c4e09a6fd66a8fd979844f69f08a"
integrity sha512-dhEPs72UPbDnAQJ9ZKMNTP6ptJaionhP5cBb541nXPlW60Jepo9RV/a4fX4XWW9CuFNK22krhrj1+rgzifNCsw==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
bytes "3.1.0"
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
content-type "~1.0.4"
debug "2.6.9"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
depd "~1.1.2"
http-errors "1.7.2"
iconv-lite "0.4.24"
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
on-finished "~2.3.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
qs "6.7.0"
raw-body "2.4.0"
type-is "~1.6.17"
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
bonjour@^3.5.0:
version "3.5.0"
resolved "https://registry.yarnpkg.com/bonjour/-/bonjour-3.5.0.tgz#8e890a183d8ee9a2393b3844c691a42bcf7bc9f5"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-jokKGD2O6aI5OzhExpGkK897yfU=
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:
array-flatten "^2.1.0"
deep-equal "^1.0.1"
dns-equal "^1.0.0"
dns-txt "^2.0.2"
multicast-dns "^6.0.1"
multicast-dns-service-types "^1.1.0"
boolbase@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/boolbase/-/boolbase-1.0.0.tgz#68dff5fbe60c51eb37725ea9e3ed310dcc1e776e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-aN/1++YMUes3cl6p4+0xDcwed24=
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
brace-expansion@^1.0.0, brace-expansion@^1.1.7:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.11"
resolved "https://registry.yarnpkg.com/brace-expansion/-/brace-expansion-1.1.11.tgz#3c7fcbf529d87226f3d2f52b966ff5271eb441dd"
integrity sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==
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:
balanced-match "^1.0.0"
concat-map "0.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
braces@^2.3.1, braces@^2.3.2:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
version "2.3.2"
resolved "https://registry.yarnpkg.com/braces/-/braces-2.3.2.tgz#5979fd3f14cd531565e5fa2df1abfff1dfaee729"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-aNdbnj9P8PjdXU4ybaWLK2IF3jc/EoDYbC7AazW6to3TRsfXxscC9UXOB5iDiEQrkyIbWp2SLQda4+QAa7nc3w==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
arr-flatten "^1.1.0"
array-unique "^0.3.2"
extend-shallow "^2.0.1"
fill-range "^4.0.0"
isobject "^3.0.1"
repeat-element "^1.1.2"
snapdragon "^0.8.1"
snapdragon-node "^2.0.1"
split-string "^3.0.2"
to-regex "^3.0.1"
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
brorand@^1.0.1:
version "1.1.0"
resolved "https://registry.yarnpkg.com/brorand/-/brorand-1.1.0.tgz#12c25efe40a45e3c323eb8675a0a0ce57b22371f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-EsJe/kCkXjwyPrhnWgoM5XsiNx8=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
browser-process-hrtime@^0.1.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "0.1.3"
resolved "https://registry.yarnpkg.com/browser-process-hrtime/-/browser-process-hrtime-0.1.3.tgz#616f00faef1df7ec1b5bf9cfe2bdc3170f26c7b4"
integrity sha512-bRFnI4NnjO6cnyLmOV/7PVoDEMJChlcfN0z4s1YMBY989/SvlfMI1lgCnkFUs53e9gQF+w7qu7XdllSTiSl8Aw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
browser-resolve@^1.11.3:
version "1.11.3"
resolved "https://registry.yarnpkg.com/browser-resolve/-/browser-resolve-1.11.3.tgz#9b7cbb3d0f510e4cb86bdbd796124d28b5890af6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-exDi1BYWB/6raKHmDTCicQfTkqwN5fioMFV4j8BsfMU4R2DK/QfZfK7kOVkmWCNANf0snkBzqGqAJBao9gZMdQ==
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:
resolve "1.1.7"
browserify-aes@^1.0.0, browserify-aes@^1.0.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/browserify-aes/-/browserify-aes-1.2.0.tgz#326734642f403dabc3003209853bb70ad428ef48"
integrity sha512-+7CHXqGuspUn/Sl5aO7Ea0xWGAtETPXNSAjHo48JfLdPWcMng33Xe4znFvQweqc/uzk5zSOI3H52CYnjCfb5hA==
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:
buffer-xor "^1.0.3"
cipher-base "^1.0.0"
create-hash "^1.1.0"
evp_bytestokey "^1.0.3"
inherits "^2.0.1"
safe-buffer "^5.0.1"
browserify-cipher@^1.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/browserify-cipher/-/browserify-cipher-1.0.1.tgz#8d6474c1b870bfdabcd3bcfcc1934a10e94f15f0"
integrity sha512-sPhkz0ARKbf4rRQt2hTpAHqn47X3llLkUGn+xEJzLjwY8LRs2p0v7ljvI5EyoRO/mexrNunNECisZs+gw2zz1w==
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:
browserify-aes "^1.0.4"
browserify-des "^1.0.0"
evp_bytestokey "^1.0.0"
browserify-des@^1.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/browserify-des/-/browserify-des-1.0.2.tgz#3af4f1f59839403572f1c66204375f7a7f703e9c"
integrity sha512-BioO1xf3hFwz4kc6iBhI3ieDFompMhrMlnDFC4/0/vd5MokpuAc3R+LYbwTA9A5Yc9pq9UYPqffKpW2ObuwX5A==
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:
cipher-base "^1.0.1"
des.js "^1.0.0"
inherits "^2.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
safe-buffer "^5.1.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
browserify-rsa@^4.0.0:
version "4.0.1"
resolved "https://registry.yarnpkg.com/browserify-rsa/-/browserify-rsa-4.0.1.tgz#21e0abfaf6f2029cf2fafb133567a701d4135524"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-IeCr+vbyApzy+vsTNWenAdQTVSQ=
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:
bn.js "^4.1.0"
randombytes "^2.0.1"
browserify-sign@^4.0.0:
version "4.0.4"
resolved "https://registry.yarnpkg.com/browserify-sign/-/browserify-sign-4.0.4.tgz#aa4eb68e5d7b658baa6bf6a57e630cbd7a93d298"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-qk62jl17ZYuqa/alfmMMvXqT0pg=
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:
bn.js "^4.1.1"
browserify-rsa "^4.0.0"
create-hash "^1.1.0"
create-hmac "^1.1.2"
elliptic "^6.0.0"
inherits "^2.0.1"
parse-asn1 "^5.0.0"
browserify-zlib@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/browserify-zlib/-/browserify-zlib-0.2.0.tgz#2869459d9aa3be245fe8fe2ca1f46e2e7f54d73f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-Z942RysHXmJrhqk88FmKBVq/v5tqmSkDz7p54G/MGyjMnCFFnC79XWNbg+Vta8W6Wb2qtSZTSxIGkJrRpCFEiA==
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:
pako "~1.0.5"
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
browserslist@^4.6.0, browserslist@^4.6.2:
version "4.6.4"
resolved "https://registry.yarnpkg.com/browserslist/-/browserslist-4.6.4.tgz#fd0638b3f8867fec2c604ed0ed9300379f8ec7c2"
integrity sha512-ErJT8qGfRt/VWHSr1HeqZzz50DvxHtr1fVL1m5wf20aGrG8e1ce8fpZ2EjZEfs09DDZYSvtRaDlMpWslBf8Low==
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:
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
caniuse-lite "^1.0.30000981"
electron-to-chromium "^1.3.188"
node-releases "^1.1.25"
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
bser@^2.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.1.0"
resolved "https://registry.yarnpkg.com/bser/-/bser-2.1.0.tgz#65fc784bf7f87c009b973c12db6546902fa9c7b5"
integrity sha512-8zsjWrQkkBoLK6uxASk1nJ2SKv97ltiGDo6A3wA0/yRPz+CwmEyDo0hUrhIuukG2JHpAl3bvFIixw2/3Hi0DOg==
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:
node-int64 "^0.4.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
buffer-from@^1.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/buffer-from/-/buffer-from-1.1.1.tgz#32713bc028f75c02fdb710d7c7bcec1f2c6070ef"
integrity sha512-MQcXEUbCKtEo7bhqEs6560Hyd4XaovZlO/k9V3hjVUF/zwW7KBVdSK4gIt/bzwS9MbR5qob+F5jusZsb0YQK2A==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
buffer-indexof@^1.0.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/buffer-indexof/-/buffer-indexof-1.1.1.tgz#52fabcc6a606d1a00302802648ef68f639da268c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-4/rOEg86jivtPTeOUUT61jJO1Ya1TrR/OkqCSZDyq84WJh3LuuiphBYJN+fm5xufIk4XAFcEwte/8WzC8If/1g==
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
buffer-xor@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/buffer-xor/-/buffer-xor-1.0.3.tgz#26e61ed1422fb70dd42e6e36729ed51d855fe8d9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-JuYe0UIvtw3ULm42cp7VHYVf6Nk=
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
buffer@^4.3.0:
version "4.9.1"
resolved "https://registry.yarnpkg.com/buffer/-/buffer-4.9.1.tgz#6d1bb601b07a4efced97094132093027c95bc298"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-bRu2AbB6TvztlwlBMgkwJ8lbwpg=
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:
base64-js "^1.0.2"
ieee754 "^1.1.4"
isarray "^1.0.0"
builtin-status-codes@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/builtin-status-codes/-/builtin-status-codes-3.0.0.tgz#85982878e21b98e1c66425e03d0174788f569ee8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-hZgoeOIbmOHGZCXgPQF0eI9Wnug=
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
bytes@3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/bytes/-/bytes-3.0.0.tgz#d32815404d689699f85a4ea4fa8755dd13a96048"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-0ygVQE1olpn4Wk6k+odV3ROpYEg=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
bytes@3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/bytes/-/bytes-3.1.0.tgz#f6cf7933a360e0588fa9fde85651cdc7f805d1f6"
integrity sha512-zauLjrfCG+xvoyaqLoV8bLVXXNGC4JqlxFCutSDWA6fJrTo2ZuvLYTqZ7aHBLZSMOopbzwv8f+wZcVzfVTI2Dg==
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
cacache@^11.3.2:
version "11.3.3"
resolved "https://registry.yarnpkg.com/cacache/-/cacache-11.3.3.tgz#8bd29df8c6a718a6ebd2d010da4d7972ae3bbadc"
integrity sha512-p8WcneCytvzPxhDvYp31PD039vi77I12W+/KfR9S8AZbaiARFBCpsPJS+9uhWfeBfeAtW7o/4vt3MUqLkbY6nA==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
bluebird "^3.5.5"
chownr "^1.1.1"
figgy-pudding "^3.5.1"
glob "^7.1.4"
graceful-fs "^4.1.15"
lru-cache "^5.1.1"
mississippi "^3.0.0"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
mkdirp "^0.5.1"
move-concurrently "^1.0.1"
promise-inflight "^1.0.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
rimraf "^2.6.3"
ssri "^6.0.1"
unique-filename "^1.1.1"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
y18n "^4.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
cache-base@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/cache-base/-/cache-base-1.0.1.tgz#0a7f46416831c8b662ee36fe4e7c59d76f666ab2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-AKcdTnFSWATd5/GCPRxr2ChwIJ85CeyrEyjRHlKxQ56d4XJMGym0uAiKn0xbLOGOl3+yRpOTi484dVCEc5AUzQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
collection-visit "^1.0.0"
component-emitter "^1.2.1"
get-value "^2.0.6"
has-value "^1.0.0"
isobject "^3.0.1"
set-value "^2.0.0"
to-object-path "^0.3.0"
union-value "^1.0.0"
unset-value "^1.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
callsites@^3.0.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/callsites/-/callsites-3.1.0.tgz#b3630abd8943432f54b3f0519238e33cd7df2f73"
integrity sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
camelcase@^5.0.0, camelcase@^5.3.1:
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
version "5.3.1"
resolved "https://registry.yarnpkg.com/camelcase/-/camelcase-5.3.1.tgz#e3c9b31569e106811df242f715725a1f4c494320"
integrity sha512-L28STB170nwWS63UjtlEOE3dldQApaJXZkOI1uMFfzf3rRuPegHaHesyee+YxQ+W6SvRDQV6UrdOdRiR153wJg==
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
caniuse-lite@^1.0.30000981:
version "1.0.30000983"
resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30000983.tgz#ab3c70061ca2a3467182a10ac75109b199b647f8"
integrity sha512-/llD1bZ6qwNkt41AsvjsmwNOoA4ZB+8iqmf5LVyeSXuBODT/hAMFNVOh84NdUzoiYiSKqo5vQ3ZzeYHSi/olDQ==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
capture-exit@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/capture-exit/-/capture-exit-2.0.0.tgz#fb953bfaebeb781f62898239dabb426d08a509a4"
integrity sha512-PiT/hQmTonHhl/HFGN+Lx3JJUznrVYJ3+AQsnthneZbvW7x+f08Tk7yLJTLEOUvBTbduLeeBkxEaYXUOUrRq6g==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
rsvp "^4.8.4"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
caseless@~0.12.0:
version "0.12.0"
resolved "https://registry.yarnpkg.com/caseless/-/caseless-0.12.0.tgz#1b681c21ff84033c826543090689420d187151dc"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-G2gcIf+EAzyCZUMJBolCDRhxUdw=
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
Remove `lint-staged` pre-commit hook (#300) Summary: This just slows down commits by a few seconds. We `check-pretty` in Travis, so this doesn’t actually catch anything—and, anecdotally, it has never caught anything for me because I automatically run `prettier` on save and also (almost) always run Travis before pushing. Test Plan: Run `git commit --amend --no-edit` and note that it is now fast! wchargin-branch: no-lint-on-commit
2018-05-26 02:25:43 +00:00
chalk@1.1.3, chalk@^1.1.3:
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
version "1.1.3"
resolved "https://registry.yarnpkg.com/chalk/-/chalk-1.1.3.tgz#a8115c55e4a702fe4d150abd3872822a7e09fc98"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-qBFcVeSnAv5NFQq9OHKCKn4J/Jg=
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:
ansi-styles "^2.2.1"
escape-string-regexp "^1.0.2"
has-ansi "^2.0.0"
strip-ansi "^3.0.0"
supports-color "^2.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
chalk@2.4.2, chalk@^2.0.0, chalk@^2.0.1, chalk@^2.1.0, chalk@^2.4.2:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "2.4.2"
resolved "https://registry.yarnpkg.com/chalk/-/chalk-2.4.2.tgz#cd42541677a54333cf541a49108c1432b44c9424"
integrity sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==
dependencies:
ansi-styles "^3.2.1"
escape-string-regexp "^1.0.5"
supports-color "^5.3.0"
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
character-entities-legacy@^1.0.0:
version "1.1.3"
resolved "https://registry.yarnpkg.com/character-entities-legacy/-/character-entities-legacy-1.1.3.tgz#3c729991d9293da0ede6dddcaf1f2ce1009ee8b4"
integrity sha512-YAxUpPoPwxYFsslbdKkhrGnXAtXoHNgYjlBM3WMXkWGTl5RsY3QmOyhwAgL8Nxm9l5LBThXGawxKPn68y6/fww==
character-entities@^1.0.0:
version "1.2.3"
resolved "https://registry.yarnpkg.com/character-entities/-/character-entities-1.2.3.tgz#bbed4a52fe7ef98cc713c6d80d9faa26916d54e6"
integrity sha512-yB4oYSAa9yLcGyTbB4ItFwHw43QHdH129IJ5R+WvxOkWlyFnR5FAaBNnUq4mcxsTVZGh28bHoeTHMKXH1wZf3w==
character-reference-invalid@^1.0.0:
version "1.1.3"
resolved "https://registry.yarnpkg.com/character-reference-invalid/-/character-reference-invalid-1.1.3.tgz#1647f4f726638d3ea4a750cf5d1975c1c7919a85"
integrity sha512-VOq6PRzQBam/8Jm6XBGk2fNEnHXAdGd6go0rtd4weAGECBamHDwwCQSOT12TACIYUZegUXnV6xBXqUssijtxIg==
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
chardet@^0.4.0:
version "0.4.2"
resolved "https://registry.yarnpkg.com/chardet/-/chardet-0.4.2.tgz#b5473b33dc97c424e5d98dc87d55d4d8a29c8bf2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-tUc7M9yXxCTl2Y3IfVXU2KKci/I=
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
chardet@^0.7.0:
version "0.7.0"
resolved "https://registry.yarnpkg.com/chardet/-/chardet-0.7.0.tgz#90094849f0937f2eedc2425d0d28a9e5f0cbad9e"
integrity sha512-mT8iDcrh03qDGRRmoA2hmBJnxpllMR+0/0qlzjqZES6NdiWDcZkCNAk4rPFZ9Q85r27unkiNNg8ZOiwZXBHwcA==
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
cheerio@^0.22.0:
version "0.22.0"
resolved "https://registry.yarnpkg.com/cheerio/-/cheerio-0.22.0.tgz#a9baa860a3f9b595a6b81b1a86873121ed3a269e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-qbqoYKP5tZWmuBsahocxIe06Jp4=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
dependencies:
css-select "~1.2.0"
dom-serializer "~0.1.0"
entities "~1.1.1"
htmlparser2 "^3.9.1"
lodash.assignin "^4.0.9"
lodash.bind "^4.1.4"
lodash.defaults "^4.0.1"
lodash.filter "^4.4.0"
lodash.flatten "^4.2.0"
lodash.foreach "^4.3.0"
lodash.map "^4.4.0"
lodash.merge "^4.4.0"
lodash.pick "^4.2.1"
lodash.reduce "^4.4.0"
lodash.reject "^4.4.0"
lodash.some "^4.4.0"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
cheerio@^1.0.0-rc.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.0-rc.3"
resolved "https://registry.yarnpkg.com/cheerio/-/cheerio-1.0.0-rc.3.tgz#094636d425b2e9c0f4eb91a46c05630c9a1a8bf6"
integrity sha512-0td5ijfUPuubwLUu0OBoe98gZj8C/AA+RW3v67GPlGOrvxWjZmBXiBCRU+I8VEiNyJzjth40POfHiz2RB3gImA==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
css-select "~1.2.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
dom-serializer "~0.1.1"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
entities "~1.1.1"
htmlparser2 "^3.9.1"
lodash "^4.15.0"
parse5 "^3.0.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
chokidar@^2.0.2, chokidar@^2.1.6:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.1.6"
resolved "https://registry.yarnpkg.com/chokidar/-/chokidar-2.1.6.tgz#b6cad653a929e244ce8a834244164d241fa954c5"
integrity sha512-V2jUo67OKkc6ySiRpJrjlpJKl9kDuG+Xb8VgsGzb+aEouhgS1D0weyPU4lEzdAcsCAvrih2J2BqyXqHWvVLw5g==
dependencies:
anymatch "^2.0.0"
async-each "^1.0.1"
braces "^2.3.2"
glob-parent "^3.1.0"
inherits "^2.0.3"
is-binary-path "^1.0.0"
is-glob "^4.0.0"
normalize-path "^3.0.0"
path-is-absolute "^1.0.0"
readdirp "^2.2.1"
upath "^1.1.1"
optionalDependencies:
fsevents "^1.2.7"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
chownr@^1.1.1:
Update better-sqlite3 to v5 When we took a dep on better-sqlite3 in #836, we used a fork, because better-sqlite3 did not yet support private in-memory databases via the `:memory:` filepath. As of better-sqlite3 v5, this has been added to mainline, so we no longer need the fork. The v4->v5 transition involves some breaking changes. The only ones that affected us were two field renames, from `lastUpdateROWID` to `lastUpdateRowid`, and `returnsData` to `reader`. Test plan: After updating the field accesses, `yarn test --full` passes. For added safety, I also blew away cache, loaded a nontrivial repository, and verified that the full cred workflow still works. cc @wchargin
2019-07-04 16:48:34 +00:00
version "1.1.2"
resolved "https://registry.yarnpkg.com/chownr/-/chownr-1.1.2.tgz#a18f1e0b269c8a6a5d3c86eb298beb14c3dd7bf6"
integrity sha512-GkfeAQh+QNy3wquu9oIZr6SS5x7wGdSgNQvD10X3r+AZr1Oys22HW8kAmDMvNg2+Dm0TeGaEuO8gFwdBXxwO8A==
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
chrome-trace-event@^1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/chrome-trace-event/-/chrome-trace-event-1.0.2.tgz#234090ee97c7d4ad1a2c4beae27505deffc608a4"
integrity sha512-9e/zx1jw7B4CO+c/RXoCsfg/x1AfUBioy4owYH0bJprEYAx5hRFLRhWBqHAG57D0ZM4H7vxbP7bPe0VwhQRYDQ==
dependencies:
tslib "^1.9.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
ci-info@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/ci-info/-/ci-info-2.0.0.tgz#67a9e964be31a51e15e5010d58e6f12834002f46"
integrity sha512-5tK7EtrZ0N+OLFMthtqOj4fI2Jeb88C4CAZPu25LDVUgXJ0A3Js4PMGqrn0JU1W0Mh1/Z8wZzYPxqUrXeBboCQ==
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
cipher-base@^1.0.0, cipher-base@^1.0.1, cipher-base@^1.0.3:
version "1.0.4"
resolved "https://registry.yarnpkg.com/cipher-base/-/cipher-base-1.0.4.tgz#8760e4ecc272f4c363532f926d874aae2c1397de"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-Kkht5ye6ZGmwv40uUDZztayT2ThLQGfnj/T71N/XzeZeo3nf8foyW7zGTsPYkEya3m5f3cAypH+qe7YOrM1U2Q==
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:
inherits "^2.0.1"
safe-buffer "^5.0.1"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
class-utils@^0.3.5:
version "0.3.6"
resolved "https://registry.yarnpkg.com/class-utils/-/class-utils-0.3.6.tgz#f93369ae8b9a7ce02fd41faad0ca83033190c463"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-qOhPa/Fj7s6TY8H8esGu5QNpMMQxz79h+urzrNYN6mn+9BnxlDGf5QZ+XeCDsxSjPqsSR56XOZOJmpeurnLMeg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
arr-union "^3.1.0"
define-property "^0.2.5"
isobject "^3.0.0"
static-extend "^0.1.1"
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
classnames@^2.2.5:
version "2.2.6"
resolved "https://registry.yarnpkg.com/classnames/-/classnames-2.2.6.tgz#43935bffdd291f326dad0a205309b38d00f650ce"
integrity sha512-JR/iSQOSt+LQIWwrwEzJ9uk0xfN3mTVYMwt1Ir5mUcSN6pU+V4zQFFaJsclJbPuAUQH+yfWef6tm7l1quW3C8Q==
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
cli-cursor@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/cli-cursor/-/cli-cursor-2.1.0.tgz#b35dac376479facc3e94747d41d0d0f5238ffcb5"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-s12sN2R5+sw+lHR9QdDQ9SOP/LU=
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:
restore-cursor "^2.0.0"
cli-width@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/cli-width/-/cli-width-2.2.0.tgz#ff19ede8a9a5e579324147b0c11f0fbcbabed639"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-/xnt6Kml5XkyQUewwR8PvLq+1jk=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
cliui@^4.0.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/cliui/-/cliui-4.1.0.tgz#348422dbe82d800b3022eef4f6ac10bf2e4d1b49"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-4FG+RSG9DL7uEwRUZXZn3SS34DiDPfzP0VOiEwtUWlE+AR2EIg+hSyvrIgUUfhdgR/UkAeW2QHgeP+hWrXs7jQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
string-width "^2.1.1"
strip-ansi "^4.0.0"
wrap-ansi "^2.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
cliui@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/cliui/-/cliui-5.0.0.tgz#deefcfdb2e800784aa34f46fa08e06851c7bbbc5"
integrity sha512-PYeGSEmmHM6zvoef2w8TPzlrnNpXIjTipYK780YswmIP9vjxmd6Y2a3CB2Ks6/AU8NHjZugXvo8w3oWM2qnwXA==
dependencies:
string-width "^3.1.0"
strip-ansi "^5.2.0"
wrap-ansi "^5.1.0"
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
co@^4.6.0:
version "4.6.0"
resolved "https://registry.yarnpkg.com/co/-/co-4.6.0.tgz#6ea6bdf3d853ae54ccb8e47bfa0bf3f9031fb184"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-bqa989hTrlTMuOR7+gvz+QMfsYQ=
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
code-point-at@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/code-point-at/-/code-point-at-1.1.0.tgz#0d070b4d043a5bea33a2f1a40e2edb3d9a4ccf77"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-DQcLTQQ6W+ozovGkDi7bPZpMz3c=
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
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
collapse-white-space@^1.0.2:
version "1.0.5"
resolved "https://registry.yarnpkg.com/collapse-white-space/-/collapse-white-space-1.0.5.tgz#c2495b699ab1ed380d29a1091e01063e75dbbe3a"
integrity sha512-703bOOmytCYAX9cXYqoikYIx6twmFCXsnzRQheBcTG3nzKYBR4P/+wkYeH+Mvj7qUz8zZDtdyzbxfnEi/kYzRQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
collection-visit@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/collection-visit/-/collection-visit-1.0.0.tgz#4bc0373c164bc3291b4d368c829cf1a80a59dca0"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-S8A3PBZLwykbTTaMgpzxqApZ3KA=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
map-visit "^1.0.0"
object-visit "^1.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
color-convert@^1.9.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.9.3"
resolved "https://registry.yarnpkg.com/color-convert/-/color-convert-1.9.3.tgz#bb71850690e1f136567de629d2d5471deda4c1e8"
integrity sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
color-name "1.1.3"
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
color-name@1.1.3:
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
version "1.1.3"
resolved "https://registry.yarnpkg.com/color-name/-/color-name-1.1.3.tgz#a7d0558bd89c42f795dd42328f740831ca53bc25"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-p9BVi9icQveV3UIyj3QIMcpTvCU=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
combined-stream@^1.0.6, combined-stream@~1.0.6:
version "1.0.8"
resolved "https://registry.yarnpkg.com/combined-stream/-/combined-stream-1.0.8.tgz#c3d45a8b34fd730631a110a8a2520682b31d5a7f"
integrity sha512-FQN4MRfuJeHf7cBbBMJFXhKSDq+2kAArBlmRBvcvFE5BB1HZKXtSFASDhdlz9zOYwxh8lDdnvmMOe/+5cdoEdg==
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:
delayed-stream "~1.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
commander@^2.11.0, commander@^2.19.0, commander@^2.20.0, commander@~2.20.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "2.20.0"
resolved "https://registry.yarnpkg.com/commander/-/commander-2.20.0.tgz#d58bb2b5c1ee8f87b0d340027e9e94e222c5a422"
integrity sha512-7j2y+40w61zy6YC2iRNpUe/NwhNyoXrYpHMrSunaMG64nRnaf96zO/KMQR4OyN/UnE5KLyEBnKHd4aG3rskjpQ==
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
commondir@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/commondir/-/commondir-1.0.1.tgz#ddd800da0c66127393cca5950ea968a3aaf1253b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-3dgA2gxmEnOTzKWVDqloo6rxJTs=
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
commonmark@^0.29.0:
version "0.29.0"
resolved "https://registry.yarnpkg.com/commonmark/-/commonmark-0.29.0.tgz#0f4b1d7bf9ae07b3b3a2d428ffd1d997b2ec7a7e"
integrity sha512-Wc3kvAIm0EK85pHsM95Fev31wEN6/zQpwd2qcLDL8psjHRoUFvUeGHevIJAdToWUuFoX8WI/gmeDauqy32xgJQ==
Add dependency on `commonmark` (#440) Summary: We plan to use this to more intelligently extract references from GitHub text content. See #432. Test Plan: In a Node shell, running ```js const cm = require("commonmark"); var parser = new cm.Parser(); var ast = parser.parse("Hello\nworld"); var html = new cm.HtmlRenderer({softbreak: " "}).render(ast); console.log(html); ``` prints `<p>Hello world</p>`. wchargin-branch: commonmark
2018-06-29 00:01:31 +00:00
dependencies:
entities "~ 1.1.1"
mdurl "~ 1.0.1"
minimist "~ 1.2.0"
string.prototype.repeat "^0.2.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
component-emitter@^1.2.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/component-emitter/-/component-emitter-1.3.0.tgz#16e4070fba8ae29b679f2215853ee181ab2eabc0"
integrity sha512-Rd3se6QB+sO1TwqZjscQrurpEPIfO0/yYnSin6Q/rD3mOutHvUrCAhJub3r90uNb+SESBuE0QYoB90YdfatsRg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
compressible@~2.0.16:
version "2.0.17"
resolved "https://registry.yarnpkg.com/compressible/-/compressible-2.0.17.tgz#6e8c108a16ad58384a977f3a482ca20bff2f38c1"
integrity sha512-BGHeLCK1GV7j1bSmQQAi26X+GgWcTjLr/0tzSvMCl3LH1w1IJ4PFSPoV5316b30cneTziC+B1a+3OjoSUcQYmw==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
mime-db ">= 1.40.0 < 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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
compression@^1.7.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.7.4"
resolved "https://registry.yarnpkg.com/compression/-/compression-1.7.4.tgz#95523eff170ca57c29a0ca41e6fe131f41e5bb8f"
integrity sha512-jaSIDzP9pZVS4ZfQ+TzvtiWhdpFhE2RDHz8QJkpX9SIpLq88VueF5jJw6t+6CUQcAoA6t+x89MLrWAqpfDE8iQ==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
accepts "~1.3.5"
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
bytes "3.0.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
compressible "~2.0.16"
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
debug "2.6.9"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
on-headers "~1.0.2"
safe-buffer "5.1.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
vary "~1.1.2"
concat-map@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/concat-map/-/concat-map-0.0.1.tgz#d8a96bd77fd68df7793a73036a3ba0d5405d477b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-2Klr13/Wjfd5OnMDajug1UBdR3s=
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
concat-stream@^1.5.0:
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
version "1.6.2"
resolved "https://registry.yarnpkg.com/concat-stream/-/concat-stream-1.6.2.tgz#904bdf194cd3122fc675c77fc4ac3d4ff0fd1a34"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-27HBghJxjiZtIk3Ycvn/4kbJk/1uZuJFfuPEns6LaEvpvG1f0hTea8lilrouyo9mVc2GWdcEZ8OLoGmSADlrCw==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
buffer-from "^1.0.0"
inherits "^2.0.3"
readable-stream "^2.2.2"
typedarray "^0.0.6"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
connect-history-api-fallback@^1.6.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.6.0"
resolved "https://registry.yarnpkg.com/connect-history-api-fallback/-/connect-history-api-fallback-1.6.0.tgz#8b32089359308d111115d81cad3fceab888f97bc"
integrity sha512-e54B99q/OUoH64zYYRf3HBP5z24G38h5D3qXu23JGRoigpX5Ss4r9ZnDk3g0Z8uQC2x2lPaJ+UlWBc1ZWBWdLg==
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
console-browserify@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/console-browserify/-/console-browserify-1.1.0.tgz#f0241c45730a9fc6323b206dbf38edc741d0bb10"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-8CQcRXMKn8YyOyBtvzjtx0HQuxA=
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:
date-now "^0.1.4"
console-control-strings@^1.0.0, console-control-strings@~1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/console-control-strings/-/console-control-strings-1.1.0.tgz#3d7cf4464db6446ea644bf4b39507f9851008e8e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-PXz0Rk22RG6mRL9LOVB/mFEAjo4=
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
constants-browserify@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/constants-browserify/-/constants-browserify-1.0.0.tgz#c20b96d8c617748aaf1c16021760cd27fcb8cb75"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-wguW2MYXdIqvHBYCF2DNJ/y4y3U=
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
contains-path@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/contains-path/-/contains-path-0.1.0.tgz#fe8cf184ff6670b6baef01a9d4861a5cbec4120a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-/ozxhP9mcLa67wGp1IYaXL7EEgo=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
content-disposition@0.5.3:
version "0.5.3"
resolved "https://registry.yarnpkg.com/content-disposition/-/content-disposition-0.5.3.tgz#e130caf7e7279087c5616c2007d0485698984fbd"
integrity sha512-ExO0774ikEObIAEV9kDo50o+79VCUdEB6n6lzKgGwupcVeRlhrj3qGAfwq8G6uBJjkqLrhT0qEYFcWng8z1z0g==
dependencies:
safe-buffer "5.1.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
content-type@~1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/content-type/-/content-type-1.0.4.tgz#e138cc75e040c727b1966fe5e5f8c9aee256fe3b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-hIP3EEPs8tB9AT1L+NUqtwOAps4mk2Zob89MWXMHjHWg9milF/j4osnnQLXBCBFBk/tvIG/tUc9mOUJiPBhPXA==
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
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
convert-source-map@^1.1.0, convert-source-map@^1.4.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "1.6.0"
resolved "https://registry.yarnpkg.com/convert-source-map/-/convert-source-map-1.6.0.tgz#51b537a8c43e0f04dec1993bffcdd504e758ac20"
integrity sha512-eFu7XigvxdZ1ETfbgPBohgyQ/Z++C0eEhTor0qRwBw9unw+L0/6V8wkSuGgzdThkiS5lSpdptOQPD8Ak40a+7A==
dependencies:
safe-buffer "~5.1.1"
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
cookie-signature@1.0.6:
version "1.0.6"
resolved "https://registry.yarnpkg.com/cookie-signature/-/cookie-signature-1.0.6.tgz#e303a882b342cc3ee8ca513a79999734dab3ae2c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-4wOogrNCzD7oylE6eZmXNNqzriw=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
cookie@0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/cookie/-/cookie-0.4.0.tgz#beb437e7022b3b6d49019d088665303ebe9c14ba"
integrity sha512-+Hp8fLp57wnUSt0tY0tHEXh4voZRDnoIrZPqlo3DPiI4y9lwg/jqx+1Om94/W6ZaPDOUbnjOt/99w66zk+l1Xg==
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
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
copy-concurrently@^1.0.0:
version "1.0.5"
resolved "https://registry.yarnpkg.com/copy-concurrently/-/copy-concurrently-1.0.5.tgz#92297398cae34937fcafd6ec8139c18051f0b5e0"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-f2domd9fsVDFtaFcbaRZuYXwtdmnzqbADSwhSWYxYB/Q8zsdUUFMXVRwXGDMWmbEzAn1kdRrtI1T/KTFOL4X2A==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
aproba "^1.1.1"
fs-write-stream-atomic "^1.0.8"
iferr "^0.1.5"
mkdirp "^0.5.1"
rimraf "^2.5.4"
run-queue "^1.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
copy-descriptor@^0.1.0:
version "0.1.1"
resolved "https://registry.yarnpkg.com/copy-descriptor/-/copy-descriptor-0.1.1.tgz#676f6eb3c39997c2ee1ac3a924fd6124748f578d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Z29us8OZl8LuGsOpJP1hJHSPV40=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
copy-webpack-plugin@^5.0.3:
version "5.0.3"
resolved "https://registry.yarnpkg.com/copy-webpack-plugin/-/copy-webpack-plugin-5.0.3.tgz#2179e3c8fd69f13afe74da338896f1f01a875b5c"
integrity sha512-PlZRs9CUMnAVylZq+vg2Juew662jWtwOXOqH4lbQD9ZFhRG9R7tVStOgHt21CBGVq7k5yIJaz8TXDLSjV+Lj8Q==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
cacache "^11.3.2"
find-cache-dir "^2.1.0"
glob-parent "^3.1.0"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
globby "^7.1.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
is-glob "^4.0.1"
loader-utils "^1.2.3"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
minimatch "^3.0.4"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
normalize-path "^3.0.0"
p-limit "^2.2.0"
schema-utils "^1.0.0"
serialize-javascript "^1.7.0"
webpack-log "^2.0.0"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
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
core-js-compat@^3.1.1:
version "3.1.4"
resolved "https://registry.yarnpkg.com/core-js-compat/-/core-js-compat-3.1.4.tgz#e4d0c40fbd01e65b1d457980fe4112d4358a7408"
integrity sha512-Z5zbO9f1d0YrJdoaQhphVAnKPimX92D6z8lCGphH89MNRxlL1prI9ExJPqVwP0/kgkQCv8c4GJGT8X16yUncOg==
dependencies:
browserslist "^4.6.2"
core-js-pure "3.1.4"
semver "^6.1.1"
core-js-pure@3.1.4:
version "3.1.4"
resolved "https://registry.yarnpkg.com/core-js-pure/-/core-js-pure-3.1.4.tgz#5fa17dc77002a169a3566cc48dc774d2e13e3769"
integrity sha512-uJ4Z7iPNwiu1foygbcZYJsJs1jiXrTTCvxfLDXNhI/I+NHbSIEyr548y4fcsCEyWY0XgfAG/qqaunJ1SThHenA==
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
core-js@^1.0.0:
version "1.2.7"
resolved "https://registry.yarnpkg.com/core-js/-/core-js-1.2.7.tgz#652294c14651db28fa93bd2d5ff2983a4f08c636"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-ZSKUwUZR2yj6k70tX/KYOk8IxjY=
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
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
core-js@^2.5.1:
version "2.6.9"
resolved "https://registry.yarnpkg.com/core-js/-/core-js-2.6.9.tgz#6b4b214620c834152e179323727fc19741b084f2"
integrity sha512-HOpZf6eXmnl7la+cUdMnLvUxKNqLUzJvgIziQ0DiF3JwSImNphIqdGqzj6hIKyX04MmV0poclQ7+wjWvxQyR2A==
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
core-util-is@1.0.2, core-util-is@~1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/core-util-is/-/core-util-is-1.0.2.tgz#b5fd54220aa2bc5ab57aab7140c940754503c1a7"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-tf1UIgqivFq1eqtxQMlAdUUDwac=
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
create-ecdh@^4.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "4.0.3"
resolved "https://registry.yarnpkg.com/create-ecdh/-/create-ecdh-4.0.3.tgz#c9111b6f33045c4697f144787f9254cdc77c45ff"
integrity sha512-GbEHQPMOswGpKXM9kCWVrremUcBmjteUaQ01T9rkKCPDXfUHX0IoP9LpHYo2NPFampa4e+/pFDc3jQdxrxQLaw==
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:
bn.js "^4.1.0"
elliptic "^6.0.0"
create-hash@^1.1.0, create-hash@^1.1.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/create-hash/-/create-hash-1.2.0.tgz#889078af11a63756bcfb59bd221996be3a9ef196"
integrity sha512-z00bCGNHDG8mHAkP7CtT1qVu+bFQUPjYq/4Iv3C3kWjTFV10zIjfSoeqXo9Asws8gwSHDGj/hl2u4OGIjapeCg==
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:
cipher-base "^1.0.1"
inherits "^2.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
md5.js "^1.3.4"
ripemd160 "^2.0.1"
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
sha.js "^2.4.0"
create-hmac@^1.1.0, create-hmac@^1.1.2, create-hmac@^1.1.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.7"
resolved "https://registry.yarnpkg.com/create-hmac/-/create-hmac-1.1.7.tgz#69170c78b3ab957147b2b8b04572e47ead2243ff"
integrity sha512-MJG9liiZ+ogc4TzUwuvbER1JRdgvUFSB5+VR/g5h82fGaIRWMWddtKBHi7/sVhfjQZ6SehlyhvQYrcYkaUIpLg==
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:
cipher-base "^1.0.3"
create-hash "^1.1.0"
inherits "^2.0.1"
ripemd160 "^2.0.0"
safe-buffer "^5.0.1"
sha.js "^2.4.8"
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
create-react-class@^15.5.1:
version "15.6.3"
resolved "https://registry.yarnpkg.com/create-react-class/-/create-react-class-15.6.3.tgz#2d73237fb3f970ae6ebe011a9e66f46dbca80036"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-M+/3Q6E6DLO6Yx3OwrWjwHBnvfXXYA7W+dFjt/ZDBemHO1DDZhsalX/NUtnTYclN6GfnBDRh4qRHjcDHmlJBJg==
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
dependencies:
fbjs "^0.8.9"
loose-envify "^1.3.1"
object-assign "^4.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
cross-fetch@^2.2.2:
version "2.2.3"
resolved "https://registry.yarnpkg.com/cross-fetch/-/cross-fetch-2.2.3.tgz#e8a0b3c54598136e037f8650f8e823ccdfac198e"
integrity sha512-PrWWNH3yL2NYIb/7WF/5vFG3DCQiXDOVf8k3ijatbrtnwNuhMWLC7YF7uqf53tbTFDzHIUD8oITw4Bxt8ST3Nw==
dependencies:
node-fetch "2.1.2"
whatwg-fetch "2.0.4"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
cross-spawn@5.1.0:
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
version "5.1.0"
resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-5.1.0.tgz#e8bd0efee58fcff6f8f94510a0a554bbfa235449"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-6L0O/uWPz/b4+UUQoKVUu/ojVEk=
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:
lru-cache "^4.0.1"
shebang-command "^1.2.0"
which "^1.2.9"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
cross-spawn@6.0.5, cross-spawn@^6.0.0, cross-spawn@^6.0.5:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "6.0.5"
resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-6.0.5.tgz#4a5ec7c64dfae22c3a14124dbacdee846d80cbc4"
integrity sha512-eTVLrBSt7fjbDygz805pMnstIs2VTBNkRm0qxZd+M7A5XDdxVRWO5MxGBXZhjY4cqLYLdtrGqRf8mBPmzwSpWQ==
dependencies:
nice-try "^1.0.4"
path-key "^2.0.1"
semver "^5.5.0"
shebang-command "^1.2.0"
which "^1.2.9"
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
crypto-browserify@^3.11.0:
version "3.12.0"
resolved "https://registry.yarnpkg.com/crypto-browserify/-/crypto-browserify-3.12.0.tgz#396cf9f3137f03e4b8e532c58f698254e00f80ec"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-fz4spIh+znjO2VjL+IdhEpRJ3YN6sMzITSBijk6FK2UvTqruSQW+/cCZTSNsMiZNvUeq0CqurF+dAbyiGOY6Wg==
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:
browserify-cipher "^1.0.0"
browserify-sign "^4.0.0"
create-ecdh "^4.0.0"
create-hash "^1.1.0"
create-hmac "^1.1.0"
diffie-hellman "^5.0.0"
inherits "^2.0.1"
pbkdf2 "^3.0.3"
public-encrypt "^4.0.0"
randombytes "^2.0.0"
randomfill "^1.0.3"
Add style support to the artifacts app Test Plan: Note that the header, when rendered, is magenta. wchargin-branch: stylish-artifacts
2018-03-19 22:31:08 +00:00
css-in-js-utils@^2.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.0.1"
resolved "https://registry.yarnpkg.com/css-in-js-utils/-/css-in-js-utils-2.0.1.tgz#3b472b398787291b47cfe3e44fecfdd9e914ba99"
integrity sha512-PJF0SpJT+WdbVVt0AOYp9C8GnuruRlL/UFW7932nLWmFLQTaWEzTBQEx7/hn4BuV+WON75iAViSUJLiU3PKbpA==
Add style support to the artifacts app Test Plan: Note that the header, when rendered, is magenta. wchargin-branch: stylish-artifacts
2018-03-19 22:31:08 +00:00
dependencies:
hyphenate-style-name "^1.0.2"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
isobject "^3.0.1"
Add style support to the artifacts app Test Plan: Note that the header, when rendered, is magenta. wchargin-branch: stylish-artifacts
2018-03-19 22:31:08 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
css-loader@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/css-loader/-/css-loader-3.0.0.tgz#bdd48a4921eefedf1f0a55266585944d4e5efc63"
integrity sha512-WR6KZuCkFbnMhRrGPlkwAA7SSCtwqPwpyXJAPhotYkYsc0mKU9n/fu5wufy4jl2WhBw9Ia8gUQMIp/1w98DuPw==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
camelcase "^5.3.1"
cssesc "^3.0.0"
icss-utils "^4.1.1"
loader-utils "^1.2.3"
normalize-path "^3.0.0"
postcss "^7.0.17"
postcss-modules-extract-imports "^2.0.0"
postcss-modules-local-by-default "^3.0.2"
postcss-modules-scope "^2.1.0"
postcss-modules-values "^3.0.0"
postcss-value-parser "^4.0.0"
schema-utils "^1.0.0"
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
deps: remove some unused packages (#789) Summary: Mostly Webpack loaders that have become unused through various config changes. Test Plan: Check that these packages are not used anywhere except as transitive dependencies: ```shell $ git show --format= package.json | > sed '1,4d' | grep '^-' | cut -d\" -f2 | git grep -cf - yarn.lock:3 ``` Also, `yarn && yarn test --full` works, and `yarn start` works, and `yarn backend && node ./bin/sourcecred.js load sourcecred/example-git` works. wchargin-branch: remove-unused-deps
2018-09-06 19:08:45 +00:00
css-select@~1.2.0:
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
version "1.2.0"
resolved "https://registry.yarnpkg.com/css-select/-/css-select-1.2.0.tgz#2b3a110539c5355f1cd8d314623e870b121ec858"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-KzoRBTnFNV8c2NMUYj6HCxIeyFg=
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:
boolbase "~1.0.0"
css-what "2.1"
domutils "1.5.1"
nth-check "~1.0.1"
css-what@2.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.1.3"
resolved "https://registry.yarnpkg.com/css-what/-/css-what-2.1.3.tgz#a6d7604573365fe74686c3f311c56513d88285f2"
integrity sha512-a+EPoD+uZiNfh+5fxw2nO9QwFa6nJe2Or35fGY6Ipw1R3R4AGz1d1TEZrCegvw2YTmZ0jXirGYlzxxpYSHwpEg==
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
Port skeleton of Odyssey frontend (#1132) This commit integrates an bare skeleton of the odyssey frontend that we implemented in the [odyssey-hackathon] repository. You can see the working frontend that we are trying to port over at [sourcecred.io/odyssey-hackathon/][scio]. The prototype in the other repository has some tooling choices which are incompatible/redundant with decisions in our codebase (sass vs aphrodite), and requires some tools not yet present here (svg-react-loader). This commit includes the build and integration work needed to port the prototype frontend into mainline SourceCred. The frontend scaffold isn't yet integrated with any "real" Odyssey data. One potential issue: right now, every page that is rendered from the SourceCred homepage is contained within a [homepage/Page], meaning that it has full SourceCred website styling, along with the SourceCred website header. The [application][scio] also has a header. Currently, I work around this by having the Odyssey UI cover up the base header (via absolute positioning), which works but is hacky. We can consider more principled solutions: - Finding a way to specify routes which aren't contained by [homepage/Page]; maybe by adding a new top-level route [here][route-alternative]. - Unify the headers for the Odyssey viewer and the page as a whole (sounds like inappropriate entanglement?) - Have a website header and also an application header (sounds ugly?) [homepage/Page]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/Page.js [route-alternative]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/createRoutes.js#L17 Test plan: Run `yarn start`, and then navigate to `localhost:8080/odyssey/`. observe that a working website is displayed, and that the cred logo next to the word "SourceCred" is loaded properly (i.e. svg-react-loader is integrated properly). Observe that there are no build/compile errors from either `yarn start` or `yarn build`. Also, observe that the UI looks passably nice, and that if the number of elements in the entity lists is larger than can be displayed, the sidebar pane scrolls independently. The UI was tested in both Chrome and Firefox. [odyssey-hackathon]: https://github.com/sourcecred/odyssey-hackathon [scio]: https://sourcecred.io/odyssey-hackathon/ Thanks to @jmnemo, as the implementation is based on [his work]. [his work]: https://github.com/jmnemo/hackathon-event/
2019-05-06 15:15:39 +00:00
css@2.2.4:
version "2.2.4"
resolved "https://registry.yarnpkg.com/css/-/css-2.2.4.tgz#c646755c73971f2bba6a601e2cf2fd71b1298929"
integrity sha512-oUnjmWpy0niI3x/mPL8dVEI1l7MnG3+HHyRPHf+YFSbK+svOhXpmSOcDURUh2aOCgl2grzrOPt1nHLuCVFULLw==
dependencies:
inherits "^2.0.3"
source-map "^0.6.1"
source-map-resolve "^0.5.2"
urix "^0.1.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
cssesc@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/cssesc/-/cssesc-3.0.0.tgz#37741919903b868565e1c09ea747445cd18983ee"
integrity sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
"cssom@>= 0.3.2 < 0.4.0", cssom@~0.3.6:
version "0.3.8"
resolved "https://registry.yarnpkg.com/cssom/-/cssom-0.3.8.tgz#9f1276f5b2b463f2114d3f2c75250af8c1a36f4a"
integrity sha512-b0tGHbfegbhPJpxpiBPU2sCkigAqtM9O121le6bbOlgyV+NyGyCmVfJ6QW9eRjz8CpNfWEOYBIMIGRYkLwsIYg==
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
cssstyle@^1.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/cssstyle/-/cssstyle-1.3.0.tgz#c36c466f7037fd30f03baa271b65f0f17b50585c"
integrity sha512-wXsoRfsRfsLVNaVzoKdqvEmK/5PFaEXNspVT22Ots6K/cnJdpoDKuQFw+qlMiXnmaif1OgeC466X1zISgAOcGg==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
cssom "~0.3.6"
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
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
cyclist@~0.2.2:
version "0.2.2"
resolved "https://registry.yarnpkg.com/cyclist/-/cyclist-0.2.2.tgz#1b33792e11e914a2fd6d6ed6447464444e5fa640"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-GzN5LhHpFKL9bW7WRHRkRE5fpkA=
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
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
d3-array@^1.2.0:
version "1.2.4"
resolved "https://registry.yarnpkg.com/d3-array/-/d3-array-1.2.4.tgz#635ce4d5eea759f6f605863dbcfc30edc737f71f"
integrity sha512-KHW6M86R+FUPYGb3R5XiYjXPq7VzwxZ22buHhAEVG5ztoEcZZMLov530mmccaqA1GghZArjQV46fuc8kUqhhHw==
"d3-array@^1.2.0 || 2", d3-array@^2.2.0:
add `analysis/timeline/interval` This commit adds an `interval` module which defines intervals (time ranges), and methods for slicing up a graph into its consistuent time intervals. This is pre-requisite work for #862. I've added a dep on d3-array. Test plan: Unit tests added; run `yarn test`
2019-07-07 14:13:12 +00:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/d3-array/-/d3-array-2.2.0.tgz#a9e966b8f8d78f0888d98db1fb840fc8da8ac5c7"
integrity sha512-eE0QmSh6xToqM3sxHiJYg/QFdNn52ZEgmFE8A8abU8GsHvsIOolqH8B70/8+VGAKm5MlwaExhqR3DLIjOJMLPA==
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
d3-collection@1:
version "1.0.7"
resolved "https://registry.yarnpkg.com/d3-collection/-/d3-collection-1.0.7.tgz#349bd2aa9977db071091c13144d5e4f16b5b310e"
integrity sha512-ii0/r5f4sjKNTfh84Di+DpztYwqKhEyUlKoPrzUFfeSkWxjW49xU2QzO9qrPrNkpdI0XJkfzvmTu8V2Zylln6A==
d3-color@1:
version "1.2.3"
resolved "https://registry.yarnpkg.com/d3-color/-/d3-color-1.2.3.tgz#6c67bb2af6df3cc8d79efcc4d3a3e83e28c8048f"
integrity sha512-x37qq3ChOTLd26hnps36lexMRhNXEtVxZ4B25rL0DVdDsGQIJGB18S7y9XDwlDD6MD/ZBzITCf4JjGMM10TZkw==
d3-format@1, d3-format@^1.3.2:
version "1.3.2"
resolved "https://registry.yarnpkg.com/d3-format/-/d3-format-1.3.2.tgz#6a96b5e31bcb98122a30863f7d92365c00603562"
integrity sha512-Z18Dprj96ExragQ0DeGi+SYPQ7pPfRMtUXtsg/ChVIKNBCzjO8XYJvRTC1usblx52lqge56V5ect+frYTQc8WQ==
d3-interpolate@1, d3-interpolate@^1.3.0:
version "1.3.2"
resolved "https://registry.yarnpkg.com/d3-interpolate/-/d3-interpolate-1.3.2.tgz#417d3ebdeb4bc4efcc8fd4361c55e4040211fd68"
integrity sha512-NlNKGopqaz9qM1PXh9gBF1KSCVh+jSFErrSlD/4hybwoNX/gt1d8CDbDW+3i+5UOHhjC6s6nMvRxcuoMVNgL2w==
dependencies:
d3-color "1"
d3-path@1:
version "1.0.7"
resolved "https://registry.yarnpkg.com/d3-path/-/d3-path-1.0.7.tgz#8de7cd693a75ac0b5480d3abaccd94793e58aae8"
integrity sha512-q0cW1RpvA5c5ma2rch62mX8AYaiLX0+bdaSM2wxSU9tXjU4DNvkx9qiUvjkuWCj3p22UO/hlPivujqMiR9PDzA==
d3-scale-chromatic@^1.3.3:
version "1.3.3"
resolved "https://registry.yarnpkg.com/d3-scale-chromatic/-/d3-scale-chromatic-1.3.3.tgz#dad4366f0edcb288f490128979c3c793583ed3c0"
integrity sha512-BWTipif1CimXcYfT02LKjAyItX5gKiwxuPRgr4xM58JwlLocWbjPLI7aMEjkcoOQXMkYsmNsvv3d2yl/OKuHHw==
dependencies:
d3-color "1"
d3-interpolate "1"
d3-scale@^2.1.0:
version "2.2.2"
resolved "https://registry.yarnpkg.com/d3-scale/-/d3-scale-2.2.2.tgz#4e880e0b2745acaaddd3ede26a9e908a9e17b81f"
integrity sha512-LbeEvGgIb8UMcAa0EATLNX0lelKWGYDQiPdHj+gLblGVhGLyNbaCn3EvrJf0A3Y/uOOU5aD6MTh5ZFCdEwGiCw==
dependencies:
d3-array "^1.2.0"
d3-collection "1"
d3-format "1"
d3-interpolate "1"
d3-time "1"
d3-time-format "2"
d3-scale@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/d3-scale/-/d3-scale-3.0.0.tgz#ddede1278ac3ea2bf3666de6ca625e20bed9b6c9"
integrity sha512-ktic5HBFlAZj2CN8CCl/p/JyY8bMQluN7+fA6ICE6yyoMOnSQAZ1Bb8/5LcNpNKMBMJge+5Vv4pWJhARYlQYFw==
dependencies:
d3-array "^1.2.0 || 2"
d3-format "1"
d3-interpolate "1"
d3-time "1"
d3-time-format "2"
d3-shape@^1.2.0:
version "1.3.5"
resolved "https://registry.yarnpkg.com/d3-shape/-/d3-shape-1.3.5.tgz#e81aea5940f59f0a79cfccac012232a8987c6033"
integrity sha512-VKazVR3phgD+MUCldapHD7P9kcrvPcexeX/PkMJmkUov4JM8IxsSg1DvbYoYich9AtdTsa5nNk2++ImPiDiSxg==
dependencies:
d3-path "1"
d3-time-format@2, d3-time-format@^2.1.3:
version "2.1.3"
resolved "https://registry.yarnpkg.com/d3-time-format/-/d3-time-format-2.1.3.tgz#ae06f8e0126a9d60d6364eac5b1533ae1bac826b"
integrity sha512-6k0a2rZryzGm5Ihx+aFMuO1GgelgIz+7HhB4PH4OEndD5q2zGn1mDfRdNrulspOfR6JXkb2sThhDK41CSK85QA==
dependencies:
d3-time "1"
d3-time@1, d3-time@^1.0.11:
add `analysis/timeline/interval` This commit adds an `interval` module which defines intervals (time ranges), and methods for slicing up a graph into its consistuent time intervals. This is pre-requisite work for #862. I've added a dep on d3-array. Test plan: Unit tests added; run `yarn test`
2019-07-07 14:13:12 +00:00
version "1.0.11"
resolved "https://registry.yarnpkg.com/d3-time/-/d3-time-1.0.11.tgz#1d831a3e25cd189eb256c17770a666368762bbce"
integrity sha512-Z3wpvhPLW4vEScGeIMUckDW7+3hWKOQfAWg/U7PlWBnQmeKQ00gCUsTtWSYulrKNA7ta8hJ+xXc6MHrMuITwEw==
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
damerau-levenshtein@^1.0.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.5"
resolved "https://registry.yarnpkg.com/damerau-levenshtein/-/damerau-levenshtein-1.0.5.tgz#780cf7144eb2e8dbd1c3bb83ae31100ccc31a414"
integrity sha512-CBCRqFnpu715iPmw1KrdOrzRqbdFwQTwAWyyyYS42+iAgHCuXZ+/TdMgQkUENPomxEz9z1BEzuQU2Xw0kUuAgA==
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
dashdash@^1.12.0:
version "1.14.1"
resolved "https://registry.yarnpkg.com/dashdash/-/dashdash-1.14.1.tgz#853cfa0f7cbe2fed5de20326b8dd581035f6e2f0"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-hTz6D3y+L+1d4gMmuN1YEDX24vA=
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:
assert-plus "^1.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
data-urls@^1.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/data-urls/-/data-urls-1.1.0.tgz#15ee0582baa5e22bb59c77140da8f9c76963bbfe"
integrity sha512-YTWYI9se1P55u58gL5GkQHW4P6VJBJ5iBT+B5a7i2Tjadhv52paJG0qHX4A0OR6/t52odI64KP2YvFpkDOi3eQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
abab "^2.0.0"
whatwg-mimetype "^2.2.0"
whatwg-url "^7.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
date-now@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/date-now/-/date-now-0.1.4.tgz#eaf439fd4d4848ad74e5cc7dbef200672b9e345b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-6vQ5/U1ISK105cx9vvIAZyueNFs=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
debug@2.6.9, debug@^2.2.0, debug@^2.3.3, debug@^2.6.0, debug@^2.6.6, debug@^2.6.8, debug@^2.6.9:
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
version "2.6.9"
resolved "https://registry.yarnpkg.com/debug/-/debug-2.6.9.tgz#5d128515df134ff327e90a4c93f4e077a536341f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==
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:
ms "2.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
debug@^3.2.5, debug@^3.2.6:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.2.6"
resolved "https://registry.yarnpkg.com/debug/-/debug-3.2.6.tgz#e83d17de16d8a7efb7717edbe5fb10135eee629b"
integrity sha512-mel+jf7nrtEl5Pn1Qx46zARXKDpBbvzezse7p7LqINmdoIk8PYP5SySaxEmYv6TZ0JyEKA1hsCId6DIhgITtWQ==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
ms "^2.1.1"
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
debug@^4.0.1, debug@^4.1.0, debug@^4.1.1:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "4.1.1"
resolved "https://registry.yarnpkg.com/debug/-/debug-4.1.1.tgz#3b72260255109c6b589cee050f1d516139664791"
integrity sha512-pYAIzeRo8J6KPEaJ0VWOh5Pzkbw/RetuzehGM7QRRX5he4fPHx2rdKMB256ehJCkX+XRQm16eZLqLNS8RSZXZw==
dependencies:
ms "^2.1.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
decamelize@^1.2.0:
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
version "1.2.0"
resolved "https://registry.yarnpkg.com/decamelize/-/decamelize-1.2.0.tgz#f6534d15148269b20352e7bee26f501f9a191290"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-9lNNFRSCabIDUue+4m9QH5oZEpA=
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
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
decimal.js-light@^2.4.1:
version "2.5.0"
resolved "https://registry.yarnpkg.com/decimal.js-light/-/decimal.js-light-2.5.0.tgz#ca7faf504c799326df94b0ab920424fdfc125348"
integrity sha512-b3VJCbd2hwUpeRGG3Toob+CRo8W22xplipNhP3tN7TSVB/cyMX71P1vM2Xjc9H74uV6dS2hDDmo/rHq8L87Upg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
decode-uri-component@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/decode-uri-component/-/decode-uri-component-0.2.0.tgz#eb3913333458775cb84cd1a1fae062106bb87545"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-6zkTMzRYd1y4TNGh+uBiEGu4dUU=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
deep-equal@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/deep-equal/-/deep-equal-1.0.1.tgz#f5d260292b660e084eff4cdbc9f08ad3247448b5"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-9dJgKStmDghO/0zbyfCK0yR0SLU=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
deep-extend@^0.6.0:
version "0.6.0"
resolved "https://registry.yarnpkg.com/deep-extend/-/deep-extend-0.6.0.tgz#c4fa7c95404a17a9c3e8ca7e1537312b736330ac"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
deep-is@~0.1.3:
version "0.1.3"
resolved "https://registry.yarnpkg.com/deep-is/-/deep-is-0.1.3.tgz#b369d6fb5dbc13eecf524f91b070feedc357cf34"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-s2nW+128E+7PUk+RsHD+7cNXzzQ=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
default-gateway@^4.2.0:
version "4.2.0"
resolved "https://registry.yarnpkg.com/default-gateway/-/default-gateway-4.2.0.tgz#167104c7500c2115f6dd69b0a536bb8ed720552b"
integrity sha512-h6sMrVB1VMWVrW13mSc6ia/DwYYw5MN6+exNu1OaJeFac5aSAvwM7lZ0NVfTABuSkQelr4h5oebg3KB1XPdjgA==
dependencies:
execa "^1.0.0"
ip-regex "^2.1.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
define-properties@^1.1.2, define-properties@^1.1.3:
version "1.1.3"
resolved "https://registry.yarnpkg.com/define-properties/-/define-properties-1.1.3.tgz#cf88da6cbee26fe6db7094f61d870cbd84cee9f1"
integrity sha512-3MqfYKj2lLzdMSf8ZIZE/V+Zuy+BgD6f164e8K2w7dgnpKArBDerGYpM46IYYcjnkdPNMjPk9A6VFB8+3SKlXQ==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
object-keys "^1.0.12"
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
define-property@^0.2.5:
version "0.2.5"
resolved "https://registry.yarnpkg.com/define-property/-/define-property-0.2.5.tgz#c35b1ef918ec3c990f9a5bc57be04aacec5c8116"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-w1se+RjsPJkPmlvFe+BKrOxcgRY=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
is-descriptor "^0.1.0"
define-property@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/define-property/-/define-property-1.0.0.tgz#769ebaaf3f4a63aad3af9e8d304c9bbe79bfb0e6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-dp66rz9KY6rTr56NMEybvnm/sOY=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
is-descriptor "^1.0.0"
define-property@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/define-property/-/define-property-2.0.2.tgz#d459689e8d654ba77e02a817f8710d702cb16e9d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-jwK2UV4cnPpbcG7+VRARKTZPUWowwXA8bzH5NP6ud0oeAxyYPuGZUAC7hMugpCdz4BeSZl2Dl9k66CHJ/46ZYQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
is-descriptor "^1.0.2"
isobject "^3.0.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
del@^4.1.1:
version "4.1.1"
resolved "https://registry.yarnpkg.com/del/-/del-4.1.1.tgz#9e8f117222ea44a31ff3a156c049b99052a9f0b4"
integrity sha512-QwGuEUouP2kVwQenAsOof5Fv8K9t3D8Ca8NxcXKrIpEHjTXK5J2nXLdP+ALI1cgv8wj7KuwBhTwBkOZSJKM5XQ==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
"@types/glob" "^7.1.1"
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
globby "^6.1.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
is-path-cwd "^2.0.0"
is-path-in-cwd "^2.0.0"
p-map "^2.0.0"
pify "^4.0.1"
rimraf "^2.6.3"
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
delayed-stream@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/delayed-stream/-/delayed-stream-1.0.0.tgz#df3ae199acadfb7d440aaae0b29e2272b24ec619"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-3zrhmayt+31ECqrgsp4icrJOxhk=
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
delegates@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/delegates/-/delegates-1.0.0.tgz#84c6e159b81904fdca59a0ef44cd870d31250f9a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-hMbhWbgZBP3KWaDvRM2HDTElD5o=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
depd@~1.1.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
version "1.1.2"
resolved "https://registry.yarnpkg.com/depd/-/depd-1.1.2.tgz#9bcd52e14c097763e749b274c4346ed2e560b5a9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-m81S4UwJd2PnSbJ0xDRu0uVgtak=
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
des.js@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/des.js/-/des.js-1.0.0.tgz#c074d2e2aa6a8a9a07dbd61f9a15c2cd83ec8ecc"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-wHTS4qpqipoH29YfmhXCzYPsjsw=
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:
inherits "^2.0.1"
minimalistic-assert "^1.0.0"
destroy@~1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/destroy/-/destroy-1.0.4.tgz#978857442c44749e4206613e37946205826abd80"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-l4hXRCxEdJ5CBmE+N5RiBYJqvYA=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
detect-file@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/detect-file/-/detect-file-1.0.0.tgz#f0d66d03672a825cb1b73bdb3fe62310c8e552b7"
integrity sha1-8NZtA2cqglyxtzvbP+YjEMjlUrc=
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
detect-libc@^1.0.2:
version "1.0.3"
resolved "https://registry.yarnpkg.com/detect-libc/-/detect-libc-1.0.3.tgz#fa137c4bd698edf55cd5cd02ac559f91a4c4ba9b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-+hN8S9aY7fVc1c0CrFWfkaTEups=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
detect-newline@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/detect-newline/-/detect-newline-2.1.0.tgz#f41f1c10be4b00e87b5f13da680759f2c5bfd3e2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-9B8cEL5LAOh7XxPaaAdZ8sW/0+I=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
detect-node@^2.0.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.0.4"
resolved "https://registry.yarnpkg.com/detect-node/-/detect-node-2.0.4.tgz#014ee8f8f669c5c58023da64b8179c083a28c46c"
integrity sha512-ZIzRpLJrOj7jjP2miAtgqIfmzbxa4ZOr5jJc601zklsfEx9oTzmmj2nVpIPRpNlRTIh8lc1kyViIY7BWSGNmKw==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
detect-port-alt@1.1.6:
version "1.1.6"
resolved "https://registry.yarnpkg.com/detect-port-alt/-/detect-port-alt-1.1.6.tgz#24707deabe932d4a3cf621302027c2b266568275"
integrity sha512-5tQykt+LqfJFBEYaDITx7S7cR7mJ/zQmLXZ2qt5w04ainYZw6tBf9dBunMjVeVOdYVRUzUOE4HkY5J7+uttb5Q==
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:
address "^1.0.1"
debug "^2.6.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
diff-sequences@^24.3.0:
version "24.3.0"
resolved "https://registry.yarnpkg.com/diff-sequences/-/diff-sequences-24.3.0.tgz#0f20e8a1df1abddaf4d9c226680952e64118b975"
integrity sha512-xLqpez+Zj9GKSnPWS0WZw1igGocZ+uua8+y+5dDNTT934N3QuY1sp2LkHzwiaYQGz60hMq0pjAshdeXm5VUOEw==
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
diffie-hellman@^5.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "5.0.3"
resolved "https://registry.yarnpkg.com/diffie-hellman/-/diffie-hellman-5.0.3.tgz#40e8ee98f55a2149607146921c63e1ae5f3d2875"
integrity sha512-kqag/Nl+f3GwyK25fhUMYj81BUOrZ9IuJsjIcDE5icNM9FJHAVm3VcUDxdLPoQtTuUylWm6ZIknYJwwaPxsUzg==
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:
bn.js "^4.1.0"
miller-rabin "^4.0.0"
randombytes "^2.0.0"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dir-glob@^2.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.2.2"
resolved "https://registry.yarnpkg.com/dir-glob/-/dir-glob-2.2.2.tgz#fa09f0694153c8918b18ba0deafae94769fc50c4"
integrity sha512-f9LBi5QWzIW3I6e//uxZoLBlUt9kcp66qo0sSCxL6YZKc75R1c4MFCoe/LaZiBGmgujvQdxc5Bn3QhfyvK5Hsw==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
path-type "^3.0.0"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
discontinuous-range@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/discontinuous-range/-/discontinuous-range-1.0.0.tgz#e38331f0844bba49b9a9cb71c771585aab1bc65a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-44Mx8IRLukm5qctxx3FYWqsbxlo=
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +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
dns-equal@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/dns-equal/-/dns-equal-1.0.0.tgz#b39e7f1da6eb0a75ba9c17324b34753c47e0654d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-s55/HabrCnW6nBcySzR1PEfgZU0=
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
dns-packet@^1.3.1:
version "1.3.1"
resolved "https://registry.yarnpkg.com/dns-packet/-/dns-packet-1.3.1.tgz#12aa426981075be500b910eedcd0b47dd7deda5a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-0UxfQkMhYAUaZI+xrNZOz/as5KgDU0M/fQ9b6SpkyLbk3GEswDi6PADJVaYJradtRVsRIlF1zLyOodbcTCDzUg==
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:
ip "^1.1.0"
safe-buffer "^5.0.1"
dns-txt@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/dns-txt/-/dns-txt-2.0.2.tgz#b91d806f5d27188e4ab3e7d107d881a1cc4642b6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-uR2Ab10nGI5Ks+fRB9iBocxGQrY=
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:
buffer-indexof "^1.0.0"
doctrine@1.5.0:
version "1.5.0"
resolved "https://registry.yarnpkg.com/doctrine/-/doctrine-1.5.0.tgz#379dce730f6166f76cefa4e6707a159b02c5a6fa"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-N53Ocw9hZvds76TmcHoVmwLFpvo=
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:
esutils "^2.0.2"
isarray "^1.0.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
doctrine@^2.1.0:
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
version "2.1.0"
resolved "https://registry.yarnpkg.com/doctrine/-/doctrine-2.1.0.tgz#5cd01fc101621b42c4cd7f5d1a66243716d3f39d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-35mSku4ZXK0vfCuHEDAwt55dg2jNajHZ1odvF+8SSr82EsZY4QmXfuWso8oEd8zRhVObSN18aM0CjSdoBX7zIw==
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:
esutils "^2.0.2"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
doctrine@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/doctrine/-/doctrine-3.0.0.tgz#addebead72a6574db783639dc87a121773973961"
integrity sha512-yS+Q5i3hBf7GBkd4KG8a7eBNNWNGLTaEwwYWUijIYM7zrlYDM0BFXHjjPWlWZ1Rg7UaddZeIDmi9jF3HmqiQ2w==
dependencies:
esutils "^2.0.2"
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
dom-helpers@^3.4.0:
version "3.4.0"
resolved "https://registry.yarnpkg.com/dom-helpers/-/dom-helpers-3.4.0.tgz#e9b369700f959f62ecde5a6babde4bccd9169af8"
integrity sha512-LnuPJ+dwqKDIyotW1VzmOZ5TONUN7CwkCR5hrgawTUbkBGYdeoNLZo6nNfGkCrjtE1nXXaj7iMMpDa8/d9WoIA==
dependencies:
"@babel/runtime" "^7.1.2"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
dom-serializer@0, dom-serializer@~0.1.0, dom-serializer@~0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/dom-serializer/-/dom-serializer-0.1.1.tgz#1ec4059e284babed36eec2941d4a970a189ce7c0"
integrity sha512-l0IU0pPzLWSHBcieZbpOKgkIn3ts3vAh7ZuFyXNwJxJXk/c4Gwj9xaTJwIDVQCXawWD0qb3IzMGH5rglQaO0XA==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
domelementtype "^1.3.0"
entities "^1.1.1"
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
domain-browser@^1.1.1:
version "1.2.0"
resolved "https://registry.yarnpkg.com/domain-browser/-/domain-browser-1.2.0.tgz#3d31f50191a6749dd1375a7f522e823d42e54eda"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-jnjyiM6eRyZl2H+W8Q/zLMA481hzi0eszAaBUzIVnmYVDBbnLxVNnfu1HgEBvCbL+71FrxMl3E6lpKH7Ge3OXA==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
domelementtype@1, domelementtype@^1.3.0, domelementtype@^1.3.1:
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
version "1.3.1"
resolved "https://registry.yarnpkg.com/domelementtype/-/domelementtype-1.3.1.tgz#d048c44b37b0d10a7f2a3d5fee3f4333d790481f"
integrity sha512-BSKB+TSpMpFI/HOxCNr1O8aMOTZ8hT3pM3GQ0w/mWRmkhEDSFJkkyzz4XQsBV44BChwGkrDfMyjVD0eA2aFV3w==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
domexception@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/domexception/-/domexception-1.0.1.tgz#937442644ca6a31261ef36e3ec677fe805582c90"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-raigMkn7CJNNo6Ihro1fzG7wr3fHuYVytzquZKX5n0yizGsTcYgzdIUwj1X9pK0VvjeihV+XiclP+DjwbsSKug==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
webidl-conversions "^4.0.2"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
domhandler@^2.3.0, domhandler@^2.4.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
version "2.4.2"
resolved "https://registry.yarnpkg.com/domhandler/-/domhandler-2.4.2.tgz#8805097e933d65e85546f726d60f5eb88b44f803"
integrity sha512-JiK04h0Ht5u/80fdLMCEmV4zkNh2BcoMFBmZ/91WtYZ8qVXSKjiw7fXMgFPnHcSZgOo3XdinHvmnDUeMf5R4wA==
dependencies:
domelementtype "1"
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
domutils@1.5.1:
version "1.5.1"
resolved "https://registry.yarnpkg.com/domutils/-/domutils-1.5.1.tgz#dcd8488a26f563d61079e48c9f7b7e32373682cf"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-3NhIiib1Y9YQeeSMn3t+Mjc2gs8=
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:
dom-serializer "0"
domelementtype "1"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
domutils@^1.5.1:
version "1.7.0"
resolved "https://registry.yarnpkg.com/domutils/-/domutils-1.7.0.tgz#56ea341e834e06e6748af7a1cb25da67ea9f8c2a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-Lgd2XcJ/NjEw+7tFvfKxOzCYKZsdct5lczQ2ZaQY8Djz7pfAD3Gbp8ySJWtreII/vDlMVmxwa6pHmdxIYgttDg==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
dom-serializer "0"
domelementtype "1"
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
dotenv-expand@5.1.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/dotenv-expand/-/dotenv-expand-5.1.0.tgz#3fbaf020bfd794884072ea26b1e9791d45a629f0"
integrity sha512-YXQl1DSa4/PQyRfgrv6aoNjhasp/p4qs9FjJ4q4cQk+8m4r6k4ZSiEyytKG8f8W9gi8WsQtIObNmKd+tMzNTmA==
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
dotenv@8.0.0:
version "8.0.0"
resolved "https://registry.yarnpkg.com/dotenv/-/dotenv-8.0.0.tgz#ed310c165b4e8a97bb745b0a9d99c31bda566440"
integrity sha512-30xVGqjLjiUOArT4+M5q9sYdvuR4riM6yK9wMcas9Vbp6zZa+ocC9dp6QoftuhTPhFAiLK/0C5Ni2nou/Bk8lg==
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
duplexer@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/duplexer/-/duplexer-0.1.1.tgz#ace6ff808c1ce66b57d1ebf97977acb02334cfc1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-rOb/gIwc5mtX0ev5eXessCM0z8E=
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
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
duplexify@^3.4.2, duplexify@^3.6.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.7.1"
resolved "https://registry.yarnpkg.com/duplexify/-/duplexify-3.7.1.tgz#2a4df5317f6ccfd91f86d6fd25d8d8a103b88309"
integrity sha512-07z8uv2wMyS51kKhD1KsdXJg5WQ6t93RneqRxUHnskXVtlYYkLqM0gqStQZ3pj073g687jPCHrqNfCzawLYh5g==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
end-of-stream "^1.0.0"
inherits "^2.0.1"
readable-stream "^2.0.0"
stream-shift "^1.0.0"
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
ecc-jsbn@~0.1.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "0.1.2"
resolved "https://registry.yarnpkg.com/ecc-jsbn/-/ecc-jsbn-0.1.2.tgz#3a83a904e54353287874c564b7549386849a98c9"
integrity sha1-OoOpBOVDUyh4dMVkt1SThoSamMk=
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:
jsbn "~0.1.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
safer-buffer "^2.1.0"
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
ee-first@1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/ee-first/-/ee-first-1.1.1.tgz#590c61156b0ae2f4f0255732a158b266bc56b21d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-WQxhFWsK4vTwJVcyoViyZrxWsh0=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
electron-to-chromium@^1.3.188:
Regenerate yarn.lock file (#1204) I've regenerated the yarn.lock file (by removing it and then re-running yarn). This picks up [a fix I authored][fix] for node-eval, which was preventing `yarn test --full` from passing in node 10 and 12. With this upgrde of transitive dependencies, we're now ready to officially support newer versions of node. Test plan: `yarn test` passes.
2019-07-06 14:02:04 +00:00
version "1.3.188"
resolved "https://registry.yarnpkg.com/electron-to-chromium/-/electron-to-chromium-1.3.188.tgz#e28e1afe4bb229989e280bfd3b395c7ec03c8b7a"
integrity sha512-tEQcughYIMj8WDMc59EGEtNxdGgwal/oLLTDw+NEqJRJwGflQvH3aiyiexrWeZOETP4/ko78PVr6gwNhdozvuQ==
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
elliptic@^6.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "6.5.0"
resolved "https://registry.yarnpkg.com/elliptic/-/elliptic-6.5.0.tgz#2b8ed4c891b7de3200e14412a5b8248c7af505ca"
integrity sha512-eFOJTMyCYb7xtE/caJ6JJu+bhi67WCYNbkGSknu20pmM8Ke/bqOfdnZWxyoGN26JgfxTbXrsCkEw4KheCT/KGg==
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:
bn.js "^4.4.0"
brorand "^1.0.1"
hash.js "^1.0.0"
hmac-drbg "^1.0.0"
inherits "^2.0.1"
minimalistic-assert "^1.0.0"
minimalistic-crypto-utils "^1.0.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
emoji-regex@^7.0.1, emoji-regex@^7.0.2:
version "7.0.3"
resolved "https://registry.yarnpkg.com/emoji-regex/-/emoji-regex-7.0.3.tgz#933a04052860c85e83c122479c4748a8e4c72156"
integrity sha512-CwBLREIQ7LvYFB0WyRvwhq5N5qPhc6PMjD6bYggFlI5YyDgl+0vxq5VHbMOFqLg7hfWzmu8T5Z1QofhmTIhItA==
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
emojis-list@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/emojis-list/-/emojis-list-2.1.0.tgz#4daa4d9db00f9819880c79fa457ae5b09a1fd389"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-TapNnbAPmBmIDHn6RXrlsJof04k=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
encodeurl@~1.0.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
version "1.0.2"
resolved "https://registry.yarnpkg.com/encodeurl/-/encodeurl-1.0.2.tgz#ad3ff4c86ec2d029322f5a02c3a9a606c95b3f59"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-rT/0yG7C0CkyL1oCw6mmBslbP1k=
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
encoding@^0.1.11:
version "0.1.12"
resolved "https://registry.yarnpkg.com/encoding/-/encoding-0.1.12.tgz#538b66f3ee62cd1ab51ec323829d1f9480c74beb"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-U4tm8+5izRq1HsMjgp0flIDHS+s=
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:
iconv-lite "~0.4.13"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
end-of-stream@^1.0.0, end-of-stream@^1.1.0:
version "1.4.1"
resolved "https://registry.yarnpkg.com/end-of-stream/-/end-of-stream-1.4.1.tgz#ed29634d19baba463b6ce6b80a37213eab71ec43"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-1MkrZNvWTKCaigbn+W15elq2BB/L22nqrSY5DKlo3X6+vclJm8Bb5djXJBmEX6fS3+zCh/F4VBK5Z2KxJt4s2Q==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
once "^1.4.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
enhanced-resolve@4.1.0, enhanced-resolve@^4.1.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/enhanced-resolve/-/enhanced-resolve-4.1.0.tgz#41c7e0bfdfe74ac1ffe1e57ad6a5c6c9f3742a7f"
integrity sha512-F/7vkyTtyc/llOIn8oWclcB25KdRaiPBpZYDgJHgh/UHtpgT2p2eldQgtQnLtUvfMKPKxbRaQM/hHkvLHt1Vng==
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:
graceful-fs "^4.1.2"
memory-fs "^0.4.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
tapable "^1.0.0"
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
Add dependency on `commonmark` (#440) Summary: We plan to use this to more intelligently extract references from GitHub text content. See #432. Test Plan: In a Node shell, running ```js const cm = require("commonmark"); var parser = new cm.Parser(); var ast = parser.parse("Hello\nworld"); var html = new cm.HtmlRenderer({softbreak: " "}).render(ast); console.log(html); ``` prints `<p>Hello world</p>`. wchargin-branch: commonmark
2018-06-29 00:01:31 +00:00
entities@^1.1.1, "entities@~ 1.1.1", entities@~1.1.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.2"
resolved "https://registry.yarnpkg.com/entities/-/entities-1.1.2.tgz#bdfa735299664dfafd34529ed4f8522a275fea56"
integrity sha512-f2LZMYl1Fzu7YSBKg+RoROelpOaNrcGmE9AZubeDfrCEia483oW4MI4VyFd5VNHIgQ/7qm1I0wUHK1eJnn2y2w==
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
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
enzyme-adapter-react-16@^1.1.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.14.0"
resolved "https://registry.yarnpkg.com/enzyme-adapter-react-16/-/enzyme-adapter-react-16-1.14.0.tgz#204722b769172bcf096cb250d33e6795c1f1858f"
integrity sha512-7PcOF7pb4hJUvjY7oAuPGpq3BmlCig3kxXGi2kFx0YzJHppqX1K8IIV9skT1IirxXlu8W7bneKi+oQ10QRnhcA==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
enzyme-adapter-utils "^1.12.0"
has "^1.0.3"
object.assign "^4.1.0"
object.values "^1.1.0"
prop-types "^15.7.2"
react-is "^16.8.6"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
react-test-renderer "^16.0.0-0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
semver "^5.7.0"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
enzyme-adapter-utils@^1.12.0:
version "1.12.0"
resolved "https://registry.yarnpkg.com/enzyme-adapter-utils/-/enzyme-adapter-utils-1.12.0.tgz#96e3730d76b872f593e54ce1c51fa3a451422d93"
integrity sha512-wkZvE0VxcFx/8ZsBw0iAbk3gR1d9hK447ebnSYBf95+r32ezBq+XDSAvRErkc4LZosgH8J7et7H7/7CtUuQfBA==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
airbnb-prop-types "^2.13.2"
function.prototype.name "^1.1.0"
object.assign "^4.1.0"
object.fromentries "^2.0.0"
prop-types "^15.7.2"
semver "^5.6.0"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
enzyme-to-json@^3.3.3:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.3.5"
resolved "https://registry.yarnpkg.com/enzyme-to-json/-/enzyme-to-json-3.3.5.tgz#f8eb82bd3d5941c9d8bc6fd9140030777d17d0af"
integrity sha512-DmH1wJ68HyPqKSYXdQqB33ZotwfUhwQZW3IGXaNXgR69Iodaoj8TF/D9RjLdz4pEhGq2Tx2zwNUIjBuqoZeTgA==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
lodash "^4.17.4"
enzyme@^3.3.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.10.0"
resolved "https://registry.yarnpkg.com/enzyme/-/enzyme-3.10.0.tgz#7218e347c4a7746e133f8e964aada4a3523452f6"
integrity sha512-p2yy9Y7t/PFbPoTvrWde7JIYB2ZyGC+NgTNbVEGvZ5/EyoYSr9aG/2rSbVvyNvMHEhw9/dmGUJHWtfQIEiX9pg==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
array.prototype.flat "^1.2.1"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
cheerio "^1.0.0-rc.2"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
function.prototype.name "^1.1.0"
has "^1.0.3"
html-element-map "^1.0.0"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
is-boolean-object "^1.0.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
is-callable "^1.1.4"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
is-number-object "^1.0.3"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
is-regex "^1.0.4"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
is-string "^1.0.4"
is-subset "^0.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
lodash.escape "^4.0.1"
lodash.isequal "^4.5.0"
object-inspect "^1.6.0"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
object-is "^1.0.1"
object.assign "^4.1.0"
object.entries "^1.0.4"
object.values "^1.0.4"
raf "^3.4.0"
rst-selector-parser "^2.2.3"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
string.prototype.trim "^1.1.2"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
errno@^0.1.3, errno@~0.1.7:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "0.1.7"
resolved "https://registry.yarnpkg.com/errno/-/errno-0.1.7.tgz#4684d71779ad39af177e3f007996f7c67c852618"
integrity sha512-MfrRBDWzIWifgq6tJj60gkAwtLNb6sQPlcFrSOflcP1aFmmruKQ2wRnze/8V6kgyz7H3FF8Npzv78mZ7XLLflg==
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:
prr "~1.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
error-ex@^1.2.0, error-ex@^1.3.1:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "1.3.2"
resolved "https://registry.yarnpkg.com/error-ex/-/error-ex-1.3.2.tgz#b4ac40648107fdcdcfae242f428bea8a14d4f1bf"
integrity sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g==
dependencies:
is-arrayish "^0.2.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
es-abstract@^1.10.0, es-abstract@^1.11.0, es-abstract@^1.12.0, es-abstract@^1.13.0, es-abstract@^1.5.0, es-abstract@^1.5.1, es-abstract@^1.7.0:
version "1.13.0"
resolved "https://registry.yarnpkg.com/es-abstract/-/es-abstract-1.13.0.tgz#ac86145fdd5099d8dd49558ccba2eaf9b88e24e9"
integrity sha512-vDZfg/ykNxQVwup/8E1BZhVzFfBxs9NqMzGcvIJrqg5k2/5Za2bWo40dK2J1pgLngZ7c+Shh8lwYtLGyrwPutg==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
es-to-primitive "^1.2.0"
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
function-bind "^1.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
has "^1.0.3"
is-callable "^1.1.4"
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
is-regex "^1.0.4"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
object-keys "^1.0.12"
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
es-to-primitive@^1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/es-to-primitive/-/es-to-primitive-1.2.0.tgz#edf72478033456e8dda8ef09e00ad9650707f377"
integrity sha512-qZryBOJjV//LaxLTV6UC//WewneB3LcXOL9NP++ozKVXsIIIpm/2c13UDiD9Jp2eThsecw9m3jPqDwTyobcdbg==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
is-callable "^1.1.4"
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
is-date-object "^1.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
is-symbol "^1.0.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
escape-html@~1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/escape-html/-/escape-html-1.0.3.tgz#0258eae4d3d0c0974de1c169188ef0051d1d1988"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Aljq5NPQwJdN4cFpGI7wBR0dGYg=
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
escape-string-regexp@1.0.5, escape-string-regexp@^1.0.2, escape-string-regexp@^1.0.5:
version "1.0.5"
resolved "https://registry.yarnpkg.com/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz#1b61c0562190a8dff6ae3bb2cf0200ca130b86d4"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-G2HAViGQqN/2rjuyzwIAyhMLhtQ=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
escodegen@^1.9.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.11.1"
resolved "https://registry.yarnpkg.com/escodegen/-/escodegen-1.11.1.tgz#c485ff8d6b4cdb89e27f4a856e91f118401ca510"
integrity sha512-JwiqFD9KdGVVpeuRa68yU3zZnBEOcPs0nKW7wZzXky8Z7tffdYUHbe11bPCV5jYlK6DVdKLWLm0f5I/QlL0Kmw==
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:
esprima "^3.1.3"
estraverse "^4.2.0"
esutils "^2.0.2"
optionator "^0.8.1"
optionalDependencies:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
source-map "~0.6.1"
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
eslint-import-resolver-node@^0.3.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
version "0.3.2"
resolved "https://registry.yarnpkg.com/eslint-import-resolver-node/-/eslint-import-resolver-node-0.3.2.tgz#58f15fb839b8d0576ca980413476aab2472db66a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-sfmTqJfPSizWu4aymbPr4Iidp5yKm8yDkHp+Ir3YiTHiiDfxh69mOUsmiqW6RZ9zRXFaF64GtYmN7e+8GHBv6Q==
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:
debug "^2.6.9"
resolve "^1.5.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
eslint-module-utils@^2.4.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.4.0"
resolved "https://registry.yarnpkg.com/eslint-module-utils/-/eslint-module-utils-2.4.0.tgz#8b93499e9b00eab80ccb6614e69f03678e84e09a"
integrity sha512-14tltLm38Eu3zS+mt0KvILC3q8jyIAH518MlG+HO0p+yK885Lb1UHTY/UgR91eOyGdmxAPb+OLoW4znqIT6Ndw==
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:
debug "^2.6.8"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
pkg-dir "^2.0.0"
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 lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
eslint-plugin-flowtype@3.12.0:
version "3.12.0"
resolved "https://registry.yarnpkg.com/eslint-plugin-flowtype/-/eslint-plugin-flowtype-3.12.0.tgz#abac9056244c4e3f8a64c9da5e1a64bff526a8e2"
integrity sha512-sqXHmT/JIxcxLU5HN5aJkyE9iNz0U0xQhgV5JoPt3SnEKSg6gSCDrZGK4o1HXuctWQoPfuotknvytVhg7P7MLQ==
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:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
lodash "^4.17.11"
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
eslint-plugin-import@2.18.0:
version "2.18.0"
resolved "https://registry.yarnpkg.com/eslint-plugin-import/-/eslint-plugin-import-2.18.0.tgz#7a5ba8d32622fb35eb9c8db195c2090bd18a3678"
integrity sha512-PZpAEC4gj/6DEMMoU2Df01C5c50r7zdGIN52Yfi7CvvWaYssG7Jt5R9nFG5gmqodxNOz9vQS87xk6Izdtpdrig==
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:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
array-includes "^3.0.3"
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
contains-path "^0.1.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
debug "^2.6.9"
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
doctrine "1.5.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
eslint-import-resolver-node "^0.3.2"
eslint-module-utils "^2.4.0"
has "^1.0.3"
lodash "^4.17.11"
minimatch "^3.0.4"
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
read-pkg-up "^2.0.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
resolve "^1.11.0"
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
eslint-plugin-jsx-a11y@6.2.3:
version "6.2.3"
resolved "https://registry.yarnpkg.com/eslint-plugin-jsx-a11y/-/eslint-plugin-jsx-a11y-6.2.3.tgz#b872a09d5de51af70a97db1eea7dc933043708aa"
integrity sha512-CawzfGt9w83tyuVekn0GDPU9ytYtxyxyFZ3aSWROmnRRFQFT2BiPJd7jvRdzNDi6oLWaS2asMeYSNMjWTV4eNg==
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:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
"@babel/runtime" "^7.4.5"
aria-query "^3.0.0"
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
array-includes "^3.0.3"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
ast-types-flow "^0.0.7"
axobject-query "^2.0.2"
damerau-levenshtein "^1.0.4"
emoji-regex "^7.0.2"
has "^1.0.3"
jsx-ast-utils "^2.2.1"
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
eslint-plugin-react@7.14.2:
version "7.14.2"
resolved "https://registry.yarnpkg.com/eslint-plugin-react/-/eslint-plugin-react-7.14.2.tgz#94c193cc77a899ac0ecbb2766fbef88685b7ecc1"
integrity sha512-jZdnKe3ip7FQOdjxks9XPN0pjUKZYq48OggNMd16Sk+8VXx6JOvXmlElxROCgp7tiUsTsze3jd78s/9AFJP2mA==
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:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
array-includes "^3.0.3"
doctrine "^2.1.0"
has "^1.0.3"
jsx-ast-utils "^2.1.0"
object.entries "^1.1.0"
object.fromentries "^2.0.0"
object.values "^1.1.0"
prop-types "^15.7.2"
resolve "^1.10.1"
eslint-scope@3.7.1:
version "3.7.1"
resolved "https://registry.yarnpkg.com/eslint-scope/-/eslint-scope-3.7.1.tgz#3d63c3edfda02e06e01a452ad88caacc7cdcb6e8"
integrity sha1-PWPD7f2gLgbgGkUq2IyqzHzctug=
dependencies:
esrecurse "^4.1.0"
estraverse "^4.1.1"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
eslint-scope@^4.0.0, eslint-scope@^4.0.3:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
version "4.0.3"
resolved "https://registry.yarnpkg.com/eslint-scope/-/eslint-scope-4.0.3.tgz#ca03833310f6889a3264781aa82e63eb9cfe7848"
integrity sha512-p7VutNr1O/QrxysMo3E45FjYDTeXBy0iTltPFNSqKAIfjDSXC+4dj+qfyuD8bfAXrW/y6lW3O76VaYNPKfpKrg==
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:
esrecurse "^4.1.0"
estraverse "^4.1.1"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
eslint-utils@^1.3.1:
version "1.3.1"
resolved "https://registry.yarnpkg.com/eslint-utils/-/eslint-utils-1.3.1.tgz#9a851ba89ee7c460346f97cf8939c7298827e512"
integrity sha512-Z7YjnIldX+2XMcjr7ZkgEsOj/bREONV60qYeB/bjMAqqqZ4zxKyWX+BOUkdmRmA9riiIPVvo5x86m5elviOk0Q==
eslint-visitor-keys@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/eslint-visitor-keys/-/eslint-visitor-keys-1.0.0.tgz#3f3180fb2e291017716acb4c9d6d5b5c34a6a81d"
integrity sha512-qzm/XxIbxm/FHyH341ZrbnMUpe+5Bocte9xkmFMzPMjRaZMcXww+MpBptFvtU+79L362nqiLhekCxCxDPaUMBQ==
eslint@6.0.1:
version "6.0.1"
resolved "https://registry.yarnpkg.com/eslint/-/eslint-6.0.1.tgz#4a32181d72cb999d6f54151df7d337131f81cda7"
integrity sha512-DyQRaMmORQ+JsWShYsSg4OPTjY56u1nCjAmICrE8vLWqyLKxhFXOthwMj1SA8xwfrv0CofLNVnqbfyhwCkaO0w==
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:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
"@babel/code-frame" "^7.0.0"
ajv "^6.10.0"
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
chalk "^2.1.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
cross-spawn "^6.0.5"
debug "^4.0.1"
doctrine "^3.0.0"
eslint-scope "^4.0.3"
eslint-utils "^1.3.1"
eslint-visitor-keys "^1.0.0"
espree "^6.0.0"
esquery "^1.0.1"
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
esutils "^2.0.2"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
file-entry-cache "^5.0.1"
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
functional-red-black-tree "^1.0.1"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
glob-parent "^3.1.0"
globals "^11.7.0"
ignore "^4.0.6"
import-fresh "^3.0.0"
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
imurmurhash "^0.1.4"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
inquirer "^6.2.2"
is-glob "^4.0.0"
js-yaml "^3.13.1"
json-stable-stringify-without-jsonify "^1.0.1"
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
levn "^0.3.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
lodash "^4.17.11"
minimatch "^3.0.4"
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
mkdirp "^0.5.1"
natural-compare "^1.4.0"
optionator "^0.8.2"
progress "^2.0.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
regexpp "^2.0.1"
semver "^5.5.1"
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
strip-ansi "^4.0.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
strip-json-comments "^2.0.1"
table "^5.2.3"
text-table "^0.2.0"
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
espree@^6.0.0:
version "6.0.0"
resolved "https://registry.yarnpkg.com/espree/-/espree-6.0.0.tgz#716fc1f5a245ef5b9a7fdb1d7b0d3f02322e75f6"
integrity sha512-lJvCS6YbCn3ImT3yKkPe0+tJ+mH6ljhGNjHQH9mRtiO6gjhVAOhVXW1yjnwqGwTkK3bGbye+hb00nFNmu0l/1Q==
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:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
acorn "^6.0.7"
acorn-jsx "^5.0.0"
eslint-visitor-keys "^1.0.0"
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
esprima@^3.1.3:
version "3.1.3"
resolved "https://registry.yarnpkg.com/esprima/-/esprima-3.1.3.tgz#fdca51cee6133895e3c88d535ce49dbff62a4633"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-/cpRzuYTOJXjyI1TXOSdv/YqRjM=
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
esprima@^4.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "4.0.1"
resolved "https://registry.yarnpkg.com/esprima/-/esprima-4.0.1.tgz#13b04cdb3e6c5d19df91ab6987a8695619b0aa71"
integrity sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
esquery@^1.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/esquery/-/esquery-1.0.1.tgz#406c51658b1f5991a5f9b62b1dc25b00e3e5c708"
integrity sha512-SmiyZ5zIWH9VM+SRUReLS5Q8a7GxtRdxEBVZpm98rJM7Sb+A9DVCndXfkeFUd3byderg+EbDkfnevfCwynWaNA==
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:
estraverse "^4.0.0"
esrecurse@^4.1.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "4.2.1"
resolved "https://registry.yarnpkg.com/esrecurse/-/esrecurse-4.2.1.tgz#007a3b9fdbc2b3bb87e4879ea19c92fdbd3942cf"
integrity sha512-64RBB++fIOAXPw3P9cy89qfMlvZEXZkqqJkjqqXIvzP5ezRZjW+lPWjw35UX/3EhUPFYbg5ER4JYgDw4007/DQ==
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:
estraverse "^4.1.0"
estraverse@^4.0.0, estraverse@^4.1.0, estraverse@^4.1.1, estraverse@^4.2.0:
version "4.2.0"
resolved "https://registry.yarnpkg.com/estraverse/-/estraverse-4.2.0.tgz#0dee3fed31fcd469618ce7342099fc1afa0bdb13"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-De4/7TH81GlhjOc0IJn8GvoL2xM=
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
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
esutils@^2.0.0, esutils@^2.0.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
version "2.0.2"
resolved "https://registry.yarnpkg.com/esutils/-/esutils-2.0.2.tgz#0abf4f1caa5bcb1f7a9d8acc6dea4faaa04bac9b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Cr9PHKpbyx96nYrMbepPqqBLrJs=
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
etag@~1.8.1:
version "1.8.1"
resolved "https://registry.yarnpkg.com/etag/-/etag-1.8.1.tgz#41ae2eeb65efa62268aebfea83ac7d79299b0887"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Qa4u62XvpiJorr/qg6x9eSmbCIc=
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
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
eval@^0.1.0:
Regenerate yarn.lock file (#1204) I've regenerated the yarn.lock file (by removing it and then re-running yarn). This picks up [a fix I authored][fix] for node-eval, which was preventing `yarn test --full` from passing in node 10 and 12. With this upgrde of transitive dependencies, we're now ready to officially support newer versions of node. Test plan: `yarn test` passes.
2019-07-06 14:02:04 +00:00
version "0.1.4"
resolved "https://registry.yarnpkg.com/eval/-/eval-0.1.4.tgz#e05dbe0dab4b9330215cbb7bf4886eb24bd58700"
integrity sha512-npGsebJejyjMRnLdFu+T/97dnigqIU0Ov3IGrZ8ygd1v7RL1vGkEKtvyWZobqUH1AQgKlg0Yqqe2BtMA9/QZLw==
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
dependencies:
require-like ">= 0.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
eventemitter3@^3.0.0:
version "3.1.2"
resolved "https://registry.yarnpkg.com/eventemitter3/-/eventemitter3-3.1.2.tgz#2d3d48f9c346698fce83a85d7d664e98535df6e7"
integrity sha512-tvtQIeLVHjDkJYnzf2dgVMxfuSGJeM/7UCG17TT4EumTfNtF+0nebF/4zWOIkCreAbtNqhGEboB6BWrwqNaw4Q==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
events@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/events/-/events-3.0.0.tgz#9a0a0dfaf62893d92b875b8f2698ca4114973e88"
integrity sha512-Dc381HFWJzEOhQ+d8pkNon++bk9h6cdAoAj4iE6Q4y6xgTzySWXlKn05/TVNpjnfRqi/X0EpJEJohPjNI3zpVA==
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
eventsource@0.1.6:
version "0.1.6"
resolved "https://registry.yarnpkg.com/eventsource/-/eventsource-0.1.6.tgz#0acede849ed7dd1ccc32c811bb11b944d4f29232"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Cs7ehJ7X3RzMMsgRuxG5RNTykjI=
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:
original ">=0.0.5"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
eventsource@^1.0.7:
version "1.0.7"
resolved "https://registry.yarnpkg.com/eventsource/-/eventsource-1.0.7.tgz#8fbc72c93fcd34088090bc0a4e64f4b5cee6d8d0"
integrity sha512-4Ln17+vVT0k8aWq+t/bF5arcS3EpT9gYtW66EPacdj/mAFevznsnyoHLPy2BA8gbIQeIHoPsvwmfBftfcG//BQ==
dependencies:
original "^1.0.0"
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
evp_bytestokey@^1.0.0, evp_bytestokey@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/evp_bytestokey/-/evp_bytestokey-1.0.3.tgz#7fcbdb198dc71959432efe13842684e0525acb02"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-/f2Go4TognH/KvCISP7OUsHn85hT9nUkxxA9BEWxFn+Oj9o8ZNLm/40hdlgSLyuOimsrTKLUMEorQexp/aPQeA==
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:
md5.js "^1.3.4"
safe-buffer "^5.1.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
exec-sh@^0.3.2:
version "0.3.2"
resolved "https://registry.yarnpkg.com/exec-sh/-/exec-sh-0.3.2.tgz#6738de2eb7c8e671d0366aea0b0db8c6f7d7391b"
integrity sha512-9sLAvzhI5nc8TpuQUh4ahMdCrWT00wPWz7j47/emR5+2qEfoZP5zzUXvx+vdx+H6ohhnsYC31iX04QLYJK8zTg==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
execa@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/execa/-/execa-1.0.0.tgz#c6236a5bb4df6d6f15e88e7f017798216749ddd8"
integrity sha512-adbxcyWV46qiHyvSp50TKt05tB4tK3HcmF7/nxfAdhnox83seTDbwnaqKO4sXRy7roHAIFqJP/Rw/AuEbX61LA==
dependencies:
cross-spawn "^6.0.0"
get-stream "^4.0.0"
is-stream "^1.1.0"
npm-run-path "^2.0.0"
p-finally "^1.0.0"
signal-exit "^3.0.0"
strip-eof "^1.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
exit@^0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/exit/-/exit-0.1.2.tgz#0632638f8d877cc82107d30a0fff1a17cba1cd0c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-BjJjj42HfMghB9MKD/8aF8uhzQw=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
expand-brackets@^2.1.4:
version "2.1.4"
resolved "https://registry.yarnpkg.com/expand-brackets/-/expand-brackets-2.1.4.tgz#b77735e315ce30f6b6eff0f83b04151a22449622"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-t3c14xXOMPa27/D4OwQVGiJEliI=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
debug "^2.3.3"
define-property "^0.2.5"
extend-shallow "^2.0.1"
posix-character-classes "^0.1.0"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.1"
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
expand-tilde@^2.0.0, expand-tilde@^2.0.2:
version "2.0.2"
resolved "https://registry.yarnpkg.com/expand-tilde/-/expand-tilde-2.0.2.tgz#97e801aa052df02454de46b02bf621642cdc8502"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-l+gBqgUt8CRU3kawK/YhZCzchQI=
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:
homedir-polyfill "^1.0.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
expect@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/expect/-/expect-24.8.0.tgz#471f8ec256b7b6129ca2524b2a62f030df38718d"
integrity sha512-/zYvP8iMDrzaaxHVa724eJBCKqSHmO0FA7EDkBiRHxg6OipmMn1fN+C8T9L9K8yr7UONkOifu6+LLH+z76CnaA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/types" "^24.8.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
ansi-styles "^3.2.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-get-type "^24.8.0"
jest-matcher-utils "^24.8.0"
jest-message-util "^24.8.0"
jest-regex-util "^24.3.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
express@^4.16.3, express@^4.17.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "4.17.1"
resolved "https://registry.yarnpkg.com/express/-/express-4.17.1.tgz#4491fc38605cf51f8629d39c2b5d026f98a4c134"
integrity sha512-mHJ9O79RqluphRrcw2X/GTh3k9tVv8YcoyY4Kkh4WDMUYKRZUq0h1o0w2rrrxBqM7VoeUVqgb27xlEMXTnYt4g==
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
accepts "~1.3.7"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
array-flatten "1.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
body-parser "1.19.0"
content-disposition "0.5.3"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
content-type "~1.0.4"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
cookie "0.4.0"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
cookie-signature "1.0.6"
debug "2.6.9"
depd "~1.1.2"
encodeurl "~1.0.2"
escape-html "~1.0.3"
etag "~1.8.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
finalhandler "~1.1.2"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
fresh "0.5.2"
merge-descriptors "1.0.1"
methods "~1.1.2"
on-finished "~2.3.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
parseurl "~1.3.3"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
path-to-regexp "0.1.7"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
proxy-addr "~2.0.5"
qs "6.7.0"
range-parser "~1.2.1"
safe-buffer "5.1.2"
send "0.17.1"
serve-static "1.14.1"
setprototypeof "1.1.1"
statuses "~1.5.0"
type-is "~1.6.18"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
utils-merge "1.0.1"
vary "~1.1.2"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
extend-shallow@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/extend-shallow/-/extend-shallow-2.0.1.tgz#51af7d614ad9a9f610ea1bafbb989d6b1c56890f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Ua99YUrZqfYQ6huvu5idaxxWiQ8=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
is-extendable "^0.1.0"
extend-shallow@^3.0.0, extend-shallow@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/extend-shallow/-/extend-shallow-3.0.2.tgz#26a71aaf073b39fb2127172746131c2704028db8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Jqcarwc7OfshJxcnRhMcJwQCjbg=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
assign-symbols "^1.0.0"
is-extendable "^1.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
extend@^3.0.0, extend@~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
version "3.0.2"
resolved "https://registry.yarnpkg.com/extend/-/extend-3.0.2.tgz#f8b1136b4071fbd8eb140aff858b1019ec2915fa"
integrity sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==
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
external-editor@^2.0.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/external-editor/-/external-editor-2.2.0.tgz#045511cfd8d133f3846673d1047c154e214ad3d5"
integrity sha512-bSn6gvGxKt+b7+6TKEv1ZycHleA7aHhRHyAqJyp5pbUFuYYNIzpZnQDk7AsYckyWdEnTeAnay0aCy2aV6iTk9A==
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:
chardet "^0.4.0"
iconv-lite "^0.4.17"
tmp "^0.0.33"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
external-editor@^3.0.3:
version "3.0.3"
resolved "https://registry.yarnpkg.com/external-editor/-/external-editor-3.0.3.tgz#5866db29a97826dbe4bf3afd24070ead9ea43a27"
integrity sha512-bn71H9+qWoOQKyZDo25mOMVpSmXROAsTJVVVYzrrtol3d4y+AsKjf4Iwl2Q+IuT0kFSQ1qo166UuIwqYq7mGnA==
dependencies:
chardet "^0.7.0"
iconv-lite "^0.4.24"
tmp "^0.0.33"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
extglob@^2.0.4:
version "2.0.4"
resolved "https://registry.yarnpkg.com/extglob/-/extglob-2.0.4.tgz#ad00fe4dc612a9232e8718711dc5cb5ab0285543"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-Nmb6QXkELsuBr24CJSkilo6UHHgbekK5UiZgfE6UHD3Eb27YC6oD+bhcT+tJ6cl8dmsgdQxnWlcry8ksBIBLpw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
array-unique "^0.3.2"
define-property "^1.0.0"
expand-brackets "^2.1.4"
extend-shallow "^2.0.1"
fragment-cache "^0.2.1"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.1"
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
extsprintf@1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/extsprintf/-/extsprintf-1.3.0.tgz#96918440e3041a7a414f8c52e3c574eb3c3e1e05"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-lpGEQOMEGnpBT4xS48V06zw+HgU=
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
extsprintf@^1.2.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/extsprintf/-/extsprintf-1.4.0.tgz#e2689f8f356fad62cca65a3a91c5df5f9551692f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-4mifjzVvrWLMplo6kcXfX5VRaS8=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
fast-deep-equal@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/fast-deep-equal/-/fast-deep-equal-2.0.1.tgz#7b05218ddf9667bf7f370bf7fdb2cb15fdd0aa49"
integrity sha1-ewUhjd+WZ79/Nwv3/bLLFf3Qqkk=
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
fast-json-stable-stringify@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/fast-json-stable-stringify/-/fast-json-stable-stringify-2.0.0.tgz#d5142c0caee6b1189f87d3a76111064f86c8bbf2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-1RQsDK7msRifh9OnYREGT4bIu/I=
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
fast-levenshtein@~2.0.4:
version "2.0.6"
resolved "https://registry.yarnpkg.com/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz#3d8a5c66883a16a30ca8643e851f19baa7797917"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-PYpcZog6FqMMqGQ+hR8Zuqd5eRc=
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
faye-websocket@^0.10.0:
version "0.10.0"
resolved "https://registry.yarnpkg.com/faye-websocket/-/faye-websocket-0.10.0.tgz#4e492f8d04dfb6f89003507f6edbf2d501e7c6f4"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-TkkvjQTftviQA1B/btvy1QHnxvQ=
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:
websocket-driver ">=0.5.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
faye-websocket@~0.11.0, faye-websocket@~0.11.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "0.11.3"
resolved "https://registry.yarnpkg.com/faye-websocket/-/faye-websocket-0.11.3.tgz#5c0e9a8968e8912c286639fde977a8b209f2508e"
integrity sha512-D2y4bovYpzziGgbHYtGCMjlJM36vAl/y+xUyn1C+FVx8szd1E+86KwVw6XvYSzOP8iMpm1X0I4xJD+QtUb36OA==
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:
websocket-driver ">=0.5.1"
fb-watchman@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/fb-watchman/-/fb-watchman-2.0.0.tgz#54e9abf7dfa2f26cd9b1636c588c1afc05de5d58"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-VOmr99+i8mzZsWNsWIwa/AXeXVg=
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:
bser "^2.0.0"
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
fbjs@^0.8.9:
version "0.8.17"
resolved "https://registry.yarnpkg.com/fbjs/-/fbjs-0.8.17.tgz#c4d598ead6949112653d6588b01a5cdcd9f90fdd"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-xNWY6taUkRJlPWWIsBpc3Nn5D90=
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
dependencies:
core-js "^1.0.0"
isomorphic-fetch "^2.1.1"
loose-envify "^1.0.0"
object-assign "^4.1.0"
promise "^7.1.1"
setimmediate "^1.0.5"
ua-parser-js "^0.7.18"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
figgy-pudding@^3.5.1:
version "3.5.1"
resolved "https://registry.yarnpkg.com/figgy-pudding/-/figgy-pudding-3.5.1.tgz#862470112901c727a0e495a80744bd5baa1d6790"
integrity sha512-vNKxJHTEKNThjfrdJwHc7brvM6eVevuO5nTj6ez8ZQ1qbXTvGthucRF7S4vf2cr71QVnT70V34v0S1DyQsti0w==
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
figures@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/figures/-/figures-2.0.0.tgz#3ab1a2d2a62c8bfb431a0c94cb797a2fce27c962"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-OrGi0qYsi/tDGgyUy3l6L84nyWI=
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:
escape-string-regexp "^1.0.5"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
file-entry-cache@^5.0.1:
version "5.0.1"
resolved "https://registry.yarnpkg.com/file-entry-cache/-/file-entry-cache-5.0.1.tgz#ca0f6efa6dd3d561333fb14515065c2fafdf439c"
integrity sha512-bCg29ictuBaKUwwArK4ouCaqDgLZcysCFLmM/Yn/FDoqndh/9vNuQfXRDvTuXKLxfD/JtZQGKFT8MGcJBK644g==
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:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
flat-cache "^2.0.1"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
file-loader@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/file-loader/-/file-loader-4.0.0.tgz#c3570783fefb6e1bc0978a856f4bf5825b966c2a"
integrity sha512-roAbL6IdSGczwfXxhMi6Zq+jD4IfUpL0jWHD7fvmjdOVb7xBfdRUHe4LpBgO23VtVK5AW1OlWZo0p34Jvx3iWg==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
loader-utils "^1.2.2"
schema-utils "^1.0.0"
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
filesize@3.5.11:
version "3.5.11"
resolved "https://registry.yarnpkg.com/filesize/-/filesize-3.5.11.tgz#1919326749433bb3cf77368bd158caabcc19e9ee"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-ZH7loueKBoDb7yG9esn1U+fgq7BzlzW6NRi5/rMdxIZ05dj7GFD/Xc5rq2CDt5Yq86CyfSYVyx4242QQNZbx1g==
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
fill-range@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/fill-range/-/fill-range-4.0.0.tgz#d544811d428f98eb06a63dc402d2403c328c38f7"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-1USBHUKPmOsGpj3EAtJAPDKMOPc=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
extend-shallow "^2.0.1"
is-number "^3.0.0"
repeat-string "^1.6.1"
to-regex-range "^2.1.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
finalhandler@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/finalhandler/-/finalhandler-1.1.2.tgz#b7e7d000ffd11938d0fdb053506f6ebabe9f587d"
integrity sha512-aAWcW57uxVNrQZqFXjITpW3sIUQmHGG3qSb9mUah9MgMC4NeWhNOlNjXEYq3HjRAvL6arUviZGGJsBg6z0zsWA==
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
dependencies:
debug "2.6.9"
encodeurl "~1.0.2"
escape-html "~1.0.3"
on-finished "~2.3.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
parseurl "~1.3.3"
statuses "~1.5.0"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
unpipe "~1.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
find-cache-dir@^2.0.0, find-cache-dir@^2.1.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
version "2.1.0"
resolved "https://registry.yarnpkg.com/find-cache-dir/-/find-cache-dir-2.1.0.tgz#8d0f94cd13fe43c6c7c261a0d86115ca918c05f7"
integrity sha512-Tq6PixE0w/VMFfCgbONnkiQIVol/JJL7nRMi20fqzA4NRs9AfeqMGeRdPi3wIhYkxjeBaWh2rxwapn5Tu3IqOQ==
dependencies:
commondir "^1.0.1"
make-dir "^2.0.0"
pkg-dir "^3.0.0"
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
find-up@^2.0.0, find-up@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/find-up/-/find-up-2.1.0.tgz#45d1b7e506c717ddd482775a2b77920a3c0c57a7"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-RdG35QbHF93UgndaK3eSCjwMV6c=
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:
locate-path "^2.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
find-up@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/find-up/-/find-up-3.0.0.tgz#49169f1d7993430646da61ecc5ae355c21c97b73"
integrity sha512-1yD6RmLI1XBfxugvORwlck6f75tYL+iR0jqwsOrOxMZyGYqUuDhJ0l4AXdO1iX/FTs9cBAMEk1gWSEx1kSbylg==
dependencies:
locate-path "^3.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
findup-sync@3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/findup-sync/-/findup-sync-3.0.0.tgz#17b108f9ee512dfb7a5c7f3c8b27ea9e1a9c08d1"
integrity sha512-YbffarhcicEhOrm4CtrwdKBdCuz576RLdhJDsIfvNtxUuhdRet1qZcsMjqbePtAseKdAnDyM/IyXbu7PRPRLYg==
dependencies:
detect-file "^1.0.0"
is-glob "^4.0.0"
micromatch "^3.0.4"
resolve-dir "^1.0.1"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
flat-cache@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/flat-cache/-/flat-cache-2.0.1.tgz#5d296d6f04bda44a4630a301413bdbc2ec085ec0"
integrity sha512-LoQe6yDuUMDzQAEH8sgmh4Md6oZnc/7PjtwjNFSzveXqSHt6ka9fPBuso7IGf9Rz4uqnSnWiFH2B/zj24a5ReA==
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:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
flatted "^2.0.0"
rimraf "2.6.3"
write "1.0.3"
flatted@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/flatted/-/flatted-2.0.1.tgz#69e57caa8f0eacbc281d2e2cb458d46fdb449e08"
integrity sha512-a1hQMktqW9Nmqr5aktAux3JMNqaucxGcjtjWnZLHX7yyPCmlSV3M54nGYbqT8K+0GhF3NBgmJCc3ma+WOgX8Jg==
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 lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
flow-bin@^0.103.0:
version "0.103.0"
resolved "https://registry.yarnpkg.com/flow-bin/-/flow-bin-0.103.0.tgz#7aec510d85e1c1b0f2b912bb988337d70035cb0f"
integrity sha512-Y3yrnE5ICN1Kl/y10BwjA3JSuS+gt4jVPNyUNCZb0RqmkdssMrW8QNNysJYvhgAY/JBJH8Qv7NVUf11MiwfSlA==
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
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
flush-write-stream@^1.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/flush-write-stream/-/flush-write-stream-1.1.1.tgz#8dd7d873a1babc207d94ead0c2e0e44276ebf2e8"
integrity sha512-3Z4XhFZ3992uIq0XOqb9AreonueSYphE6oYbpt5+3u06JWklbsPkNv3ZKkP9Bz/r+1MWCaMoSQ28P85+1Yc77w==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
inherits "^2.0.3"
readable-stream "^2.3.6"
follow-redirects@^1.0.0:
version "1.7.0"
resolved "https://registry.yarnpkg.com/follow-redirects/-/follow-redirects-1.7.0.tgz#489ebc198dc0e7f64167bd23b03c4c19b5784c76"
integrity sha512-m/pZQy4Gj287eNy94nivy5wchN3Kp+Q5WgUPNy5lJSZ3sgkVKSYV/ZChMAQVIgx1SqfZ2zBZtPA2YlXIWxxJOQ==
dependencies:
debug "^3.2.6"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
for-in@^1.0.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
version "1.0.2"
resolved "https://registry.yarnpkg.com/for-in/-/for-in-1.0.2.tgz#81068d295a8142ec0ac726c6e2200c30fb6d5e80"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-gQaNKVqBQuwKxybG4iAMMPttXoA=
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
forever-agent@~0.6.1:
version "0.6.1"
resolved "https://registry.yarnpkg.com/forever-agent/-/forever-agent-0.6.1.tgz#fbc71f0c41adeb37f96c577ad1ed42d8fdacca91"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-+8cfDEGt6zf5bFd60e1C2P2sypE=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
form-data@~2.3.2:
version "2.3.3"
resolved "https://registry.yarnpkg.com/form-data/-/form-data-2.3.3.tgz#dcce52c05f644f298c6a7ab936bd724ceffbf3a6"
integrity sha512-1lLKB2Mu3aGP1Q/2eCOx0fNbRMe7XdwktwOruhfqqd0rIJWwN4Dh+E3hrPSlDCXnSR7UtZ1N38rVXm+6+MEhJQ==
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:
asynckit "^0.4.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
combined-stream "^1.0.6"
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
mime-types "^2.1.12"
forwarded@~0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/forwarded/-/forwarded-0.1.2.tgz#98c23dab1175657b8c0573e8ceccd91b0ff18c84"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-mMI9qxF1ZXuMBXPozszZGw/xjIQ=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
fragment-cache@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/fragment-cache/-/fragment-cache-0.2.1.tgz#4290fad27f13e89be7f33799c6bc5a0abfff0d19"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-QpD60n8T6Jvn8zeZxrxaCr//DRk=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
map-cache "^0.2.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
fresh@0.5.2:
version "0.5.2"
resolved "https://registry.yarnpkg.com/fresh/-/fresh-0.5.2.tgz#3d8cadd90d976569fa835ab1f8e4b23a105605a7"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-PYyt2Q2XZWn6g1qx+OSyOhBWBac=
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
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
from2@^2.1.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/from2/-/from2-2.3.0.tgz#8bfb5502bde4a4d36cfdeea007fcca21d7e382af"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-i/tVAr3kpNNs/e6gB/zKIdfjgq8=
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
inherits "^2.0.1"
readable-stream "^2.0.0"
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
fs-extra@8.1.0:
version "8.1.0"
resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-8.1.0.tgz#49d43c45a88cd9677668cb7be1b46efdb8d2e1c0"
integrity sha512-yhlQgA6mnOJUKOsRUFsgJdQCvkKhcz8tlZG5HBQfReYZy46OwLcY+Zia0mtdHsOo9y/hP+CxMN0TU9QxoOtG4g==
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:
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
graceful-fs "^4.2.0"
jsonfile "^4.0.0"
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
universalify "^0.1.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
fs-extra@^7.0.0:
version "7.0.1"
resolved "https://registry.yarnpkg.com/fs-extra/-/fs-extra-7.0.1.tgz#4f189c44aa123b895f722804f55ea23eadc348e9"
integrity sha512-YJDaCJZEnBmcbw13fvdAM9AwNOJwOzrE4pqMqBq5nFiEqXUqHwlK4B+3pUw6JNvfSPtX05xFHtYy/1ni01eGCw==
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:
graceful-fs "^4.1.2"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
jsonfile "^4.0.0"
universalify "^0.1.0"
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
fs-minipass@^1.2.5:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.2.6"
resolved "https://registry.yarnpkg.com/fs-minipass/-/fs-minipass-1.2.6.tgz#2c5cc30ded81282bfe8a0d7c7c1853ddeb102c07"
integrity sha512-crhvyXcMejjv3Z5d2Fa9sf5xLYVCF5O1c71QxbVnbLsmYMBEvDAftewesN/HhY03YRoA7zOMxjNGrF5svGaaeQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
minipass "^2.2.1"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
fs-write-stream-atomic@^1.0.8:
version "1.0.10"
resolved "https://registry.yarnpkg.com/fs-write-stream-atomic/-/fs-write-stream-atomic-1.0.10.tgz#b47df53493ef911df75731e70a9ded0189db40c9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-tH31NJPvkR33VzHnCp3tAYnbQMk=
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
graceful-fs "^4.1.2"
iferr "^0.1.5"
imurmurhash "^0.1.4"
readable-stream "1 || 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
fs.realpath@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/fs.realpath/-/fs.realpath-1.0.0.tgz#1504ad2523158caa40db4a2787cb01411994ea4f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-FQStJSMVjKpA20onh8sBQRmU6k8=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
fsevents@^1.2.7:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "1.2.9"
resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-1.2.9.tgz#3f5ed66583ccd6f400b5a00db6f7e861363e388f"
integrity sha512-oeyj2H3EjjonWcFjD5NvZNE9Rqe4UW+nQBU2HNeKw0koVLEFIhtyETyAakeAM3de7Z/SW5kcA+fZUait9EApnw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
nan "^2.12.1"
node-pre-gyp "^0.12.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
function-bind@^1.0.2, function-bind@^1.1.1:
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
version "1.1.1"
resolved "https://registry.yarnpkg.com/function-bind/-/function-bind-1.1.1.tgz#a56899d3ea3c9bab874bb9773b7c5ede92f4895d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-yIovAzMX49sF8Yl58fSCWJ5svSLuaibPxXQJFLmBObTuCr0Mf1KiPopGM9NiFjiYBCbfaa2Fh6breQ6ANVTI0A==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
function.prototype.name@^1.1.0:
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
version "1.1.0"
resolved "https://registry.yarnpkg.com/function.prototype.name/-/function.prototype.name-1.1.0.tgz#8bd763cc0af860a859cc5d49384d74b932cd2327"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-Bs0VRrTz4ghD8pTmbJQD1mZ8A/mN0ur/jGz+A6FBxPDUPkm1tNfF6bhTYPA7i7aF4lZJVr+OXTNNrnnIl58Wfg==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
define-properties "^1.1.2"
function-bind "^1.1.1"
is-callable "^1.1.3"
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
functional-red-black-tree@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/functional-red-black-tree/-/functional-red-black-tree-1.0.1.tgz#1b0ab3bd553b2a0d6399d29c0e3ea0b252078327"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-GwqzvVU7Kg1jmdKcDj6gslIHgyc=
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
gauge@~2.7.3:
version "2.7.4"
resolved "https://registry.yarnpkg.com/gauge/-/gauge-2.7.4.tgz#2c03405c7538c39d7eb37b317022e325fb018bf7"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-LANAXHU4w51+s3sxcCLjJfsBi/c=
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:
aproba "^1.0.3"
console-control-strings "^1.0.0"
has-unicode "^2.0.0"
object-assign "^4.1.0"
signal-exit "^3.0.0"
string-width "^1.0.1"
strip-ansi "^3.0.1"
wide-align "^1.1.0"
get-caller-file@^1.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/get-caller-file/-/get-caller-file-1.0.3.tgz#f978fa4c90d1dfe7ff2d6beda2a515e713bdcf4a"
integrity sha512-3t6rVToeoZfYSGd8YoLFR2DJkiQrIiUrGcjvFX2mDw3bn6k2OtwHN0TNCLbBO+w8qTvimhDkv+LSscbJY1vE6w==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
get-caller-file@^2.0.1:
version "2.0.5"
resolved "https://registry.yarnpkg.com/get-caller-file/-/get-caller-file-2.0.5.tgz#4f94412a82db32f36e3b0b9741f8a97feb031f7e"
integrity sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
get-stream@^4.0.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-4.1.0.tgz#c1b255575f3dc21d59bfc79cd3d2b46b1c3a54b5"
integrity sha512-GMat4EJ5161kIy2HevLlr4luNjBgvmj413KaQA7jt4V8B4RDsfpHk7WQ9GVqfYyyx8OS/L66Kox+rJRNklLK7w==
dependencies:
pump "^3.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
get-value@^2.0.3, get-value@^2.0.6:
version "2.0.6"
resolved "https://registry.yarnpkg.com/get-value/-/get-value-2.0.6.tgz#dc15ca1c672387ca76bd37ac0a395ba2042a2c28"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-3BXKHGcjh8p2vTesCjlbogQqLCg=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
getpass@^0.1.1:
version "0.1.7"
resolved "https://registry.yarnpkg.com/getpass/-/getpass-0.1.7.tgz#5eff8e3e684d569ae4cb2b1282604e8ba62149fa"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Xv+OPmhNVprkyysSgmBOi6YhSfo=
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:
assert-plus "^1.0.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
glob-parent@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/glob-parent/-/glob-parent-3.1.0.tgz#9e6af6299d8d3bd2bd40430832bd113df906c5ae"
integrity sha1-nmr2KZ2NO9K9QEMIMr0RPfkGxa4=
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
is-glob "^3.1.0"
path-dirname "^1.0.0"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
glob@^7.0.3, glob@^7.1.1, glob@^7.1.2, glob@^7.1.3, glob@^7.1.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "7.1.4"
resolved "https://registry.yarnpkg.com/glob/-/glob-7.1.4.tgz#aa608a2f6c577ad357e1ae5a5c26d9a8d1969255"
integrity sha512-hkLPepehmnKk41pUGm3sYxoFs/umurYfYJCerbXEyFIWcAzvpipAgVkBqqT9RBKMGjnq6kMuyYwha6csxbiM1A==
Add CLI command to clear sourcecred data directory (#1111) Resolves #1067 Adds the CLI commands: `sourcecred clear --all` -- removes the $SOURCECRED_DIRECTORY `sourcecred clear --cache` -- removes the cache directory `sourcecred clear --help` -- provides usage info `sourcecred clear` -- prompts the user to be more specific Test plan: The unit tests ensure that the command is properly wired into the sourcecred CLI, including help text integration. However, just to be safe, we can start by verifying that calling `sourcecred` without arguments lists the `clear` command as a valid option, and that calling `sourcecred help clear` prints help information. (Note: it's necessary to run `yarn backend` before testing these changes) The unit tests also ensure that the command removes the proper directories, so there isn't really a need to manually test it, although the reviewer may choose to do so to be safe. Although out of scope for unit tests on this function, we can also do integration tests, to make sure that running the clear command doesn't leave the sourcecred directory in an invalid state from the perspective of the `load` command. ```js $ yarn backend; $ node bin/sourcecred.js load sourcecred/example-github; $ node bin/sourcecred.js clear --cache; $ node bin/sourcecred.js load sourcecred/example-github; $ node bin/sourcecred.js clear --all; $ node bin/sourcecred.js load sourcecred/example-github; ``` The expected behavior of the above command block is that the load command never fails or throws an error. @decentralion and I discussed the scenario where `rimraf` errors. We decided that testing this scenario wasn't necessary, because `rimraf` doesn't error if a directory doesn't exist, and rimraf's maintainer suggests [monkey-patching the fs module] to get rimraf to error in testing scenarios. Thanks @decentralion for reviewing and pair-programming this with me. [monkey-patching the fs module]: https://github.com/isaacs/rimraf/issues/31#issuecomment-29534796
2019-05-13 09:59:58 +00:00
dependencies:
fs.realpath "^1.0.0"
inflight "^1.0.4"
inherits "2"
minimatch "^3.0.4"
once "^1.3.0"
path-is-absolute "^1.0.0"
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
global-modules@1.0.0, global-modules@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/global-modules/-/global-modules-1.0.0.tgz#6d770f0eb523ac78164d72b5e71a8877265cc3ea"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-sKzpEkf11GpOFuw0Zzjzmt4B4UZwjOcG757PPvrfhxcLFbq0wpsgpOqxpxtxFiCG4DtG93M6XRVbF2oGdev7bg==
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:
global-prefix "^1.0.1"
is-windows "^1.0.1"
resolve-dir "^1.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
global-modules@2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/global-modules/-/global-modules-2.0.0.tgz#997605ad2345f27f51539bea26574421215c7780"
integrity sha512-NGbfmJBp9x8IxyJSd1P+otYK8vonoJactOogrVfFRIAEY1ukil8RSKDz2Yo7wh1oihl51l/r6W4epkeKJHqL8A==
dependencies:
global-prefix "^3.0.0"
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
global-prefix@^1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/global-prefix/-/global-prefix-1.0.2.tgz#dbf743c6c14992593c655568cb66ed32c0122ebe"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-2/dDxsFJklk8ZVVoy2btMsASLr4=
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:
expand-tilde "^2.0.2"
homedir-polyfill "^1.0.1"
ini "^1.3.4"
is-windows "^1.0.1"
which "^1.2.14"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
global-prefix@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/global-prefix/-/global-prefix-3.0.0.tgz#fc85f73064df69f50421f47f883fe5b913ba9b97"
integrity sha512-awConJSVCHVGND6x3tmMaKcQvwXLhjdkmomy2W+Goaui8YPgYgXJZewhg3fWC+DlfqqQuWg8AwqjGTD2nAPVWg==
dependencies:
ini "^1.3.5"
kind-of "^6.0.2"
which "^1.3.1"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
globals@^11.1.0, globals@^11.7.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "11.12.0"
resolved "https://registry.yarnpkg.com/globals/-/globals-11.12.0.tgz#ab8795338868a0babd8525758018c2a7eb95c42e"
integrity sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==
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
globby@^6.1.0:
version "6.1.0"
resolved "https://registry.yarnpkg.com/globby/-/globby-6.1.0.tgz#f5a6d70e8395e21c858fb0489d64df02424d506c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-9abXDoOV4hyFj7BInWTfAkJNUGw=
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:
array-union "^1.0.1"
glob "^7.0.3"
object-assign "^4.0.1"
pify "^2.0.0"
pinkie-promise "^2.0.0"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
globby@^7.1.1:
version "7.1.1"
resolved "https://registry.yarnpkg.com/globby/-/globby-7.1.1.tgz#fb2ccff9401f8600945dfada97440cca972b8680"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-+yzP+UAfhgCUXfral0QMypcrhoA=
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
array-union "^1.0.1"
dir-glob "^2.0.0"
glob "^7.1.2"
ignore "^3.3.5"
pify "^3.0.0"
slash "^1.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
graceful-fs@^4.1.11, graceful-fs@^4.1.15, graceful-fs@^4.1.2, graceful-fs@^4.1.6, graceful-fs@^4.2.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "4.2.0"
resolved "https://registry.yarnpkg.com/graceful-fs/-/graceful-fs-4.2.0.tgz#8d8fdc73977cb04104721cb53666c1ca64cd328b"
integrity sha512-jpSvDPV4Cq/bgtpndIWbI5hmYxhQGHPC4d4cqBPb4DLniCfhJokdXhwhaDuLBGLQdvvRum/UiX6ECVIPvDXqdg==
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
growly@^1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/growly/-/growly-1.3.0.tgz#f10748cbe76af964b7c96c93c6bcc28af120c081"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-8QdIy+dq+WS3yWyTxrzCivEgwIE=
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
gzip-size@3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/gzip-size/-/gzip-size-3.0.0.tgz#546188e9bdc337f673772f81660464b389dce520"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-VGGI6b3DN/Zzdy+BZgRks4nc5SA=
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:
duplexer "^0.1.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
handle-thing@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/handle-thing/-/handle-thing-2.0.0.tgz#0e039695ff50c93fc288557d696f3c1dc6776754"
integrity sha512-d4sze1JNC454Wdo2fkuyzCr6aHcbL6PGGuFAz0Li/NcOm1tCHGnWDRmJP85dh9IhQErTc2svWFEX5xHIOo//kQ==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
handlebars@^4.1.2:
version "4.1.2"
resolved "https://registry.yarnpkg.com/handlebars/-/handlebars-4.1.2.tgz#b6b37c1ced0306b221e094fc7aca3ec23b131b67"
integrity sha512-nvfrjqvt9xQ8Z/w0ijewdD/vvWDTOweBUm96NTr66Wfvo1mJenBLwcYmPs3TIBP5ruzYGD7Hx/DaM9RmhroGPw==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
neo-async "^2.6.0"
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
optimist "^0.6.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
source-map "^0.6.1"
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
optionalDependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
uglify-js "^3.1.4"
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
har-schema@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/har-schema/-/har-schema-2.0.0.tgz#a94c2224ebcac04782a0d9035521f24735b7ec92"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-qUwiJOvKwEeCoNkDVSHyRzW37JI=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
har-validator@~5.1.0:
version "5.1.3"
resolved "https://registry.yarnpkg.com/har-validator/-/har-validator-5.1.3.tgz#1ef89ebd3e4996557675eed9893110dc350fa080"
integrity sha512-sNvOCzEQNr/qrvJgc3UG/kD4QtlHycrzwS+6mfTrrSq97BvaYcPZZI1ZSqGSPR73Cxn4LKTD4PttRwfU7jWq5g==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
ajv "^6.5.5"
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
har-schema "^2.0.0"
has-ansi@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/has-ansi/-/has-ansi-2.0.0.tgz#34f5049ce1ecdf2b0649af3ef24e45ed35416d91"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-NPUEnOHs3ysGSa8+8k5F7TVBbZE=
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:
ansi-regex "^2.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
has-flag@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/has-flag/-/has-flag-3.0.0.tgz#b5d454dc2199ae225699f3467e5a07f3b955bafd"
integrity sha1-tdRU3CGZriJWmfNGfloH87lVuv0=
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
has-symbols@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/has-symbols/-/has-symbols-1.0.0.tgz#ba1a8f1af2a0fc39650f5c850367704122063b44"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-uhqPGvKg/DllD1yFA2dwQSIGO0Q=
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +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
has-unicode@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/has-unicode/-/has-unicode-2.0.1.tgz#e0e6fe6a28cf51138855e086d1691e771de2a8b9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-4Ob+aijPUROIVeCG0Wkedx3iqLk=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
has-value@^0.3.1:
version "0.3.1"
resolved "https://registry.yarnpkg.com/has-value/-/has-value-0.3.1.tgz#7b1f58bada62ca827ec0a2078025654845995e1f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-ex9YutpiyoJ+wKIHgCVlSEWZXh8=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
get-value "^2.0.3"
has-values "^0.1.4"
isobject "^2.0.0"
has-value@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/has-value/-/has-value-1.0.0.tgz#18b281da585b1c5c51def24c930ed29a0be6b177"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-GLKB2lhbHFxR3vJMkw7SmgvmsXc=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
get-value "^2.0.6"
has-values "^1.0.0"
isobject "^3.0.0"
has-values@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/has-values/-/has-values-0.1.4.tgz#6d61de95d91dfca9b9a02089ad384bff8f62b771"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-bWHeldkd/Km5oCCJrThL/49it3E=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
has-values@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/has-values/-/has-values-1.0.0.tgz#95b0b63fec2146619a6fe57fe75628d5a39efe4f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-lbC2P+whRmGab+V/51Yo1aOe/k8=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
is-number "^3.0.0"
kind-of "^4.0.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
has@^1.0.1, has@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/has/-/has-1.0.3.tgz#722d7cbfc1f6aa8241f16dd814e011e1f41e8796"
integrity sha512-f2dvO0VU6Oej7RkWJGrehjbzMAjFp5/VKPp5tTpWIV4JHHZK1/BxbFRtf/siA2SWTe09caDmVtYYzWEIbBS4zw==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
function-bind "^1.1.1"
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
hash-base@^3.0.0:
version "3.0.4"
resolved "https://registry.yarnpkg.com/hash-base/-/hash-base-3.0.4.tgz#5fc8686847ecd73499403319a6b0a3f3f6ae4918"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-X8hoaEfs1zSZQDMZprCj8/auSRg=
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:
inherits "^2.0.1"
safe-buffer "^5.0.1"
hash.js@^1.0.0, hash.js@^1.0.3:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.7"
resolved "https://registry.yarnpkg.com/hash.js/-/hash.js-1.1.7.tgz#0babca538e8d4ee4a0f8988d68866537a003cf42"
integrity sha512-taOaskGt4z4SOANNseOviYDvjEJinIkRgmp7LbKP2YTTmVxWBl87s/uzK9r+44BclBSp2X7K1hqeNfz9JbBeXA==
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:
inherits "^2.0.3"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
minimalistic-assert "^1.0.1"
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
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
history@^3.0.0:
version "3.3.0"
resolved "https://registry.yarnpkg.com/history/-/history-3.3.0.tgz#fcedcce8f12975371545d735461033579a6dae9c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-/O3M6PEpdTcVRdc1RhAzV5ptrpw=
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
dependencies:
invariant "^2.2.1"
loose-envify "^1.2.0"
query-string "^4.2.2"
warning "^3.0.0"
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
hmac-drbg@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/hmac-drbg/-/hmac-drbg-1.0.1.tgz#d2745701025a6c775a6c545793ed502fc0c649a1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-0nRXAQJabHdabFRXk+1QL8DGSaE=
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:
hash.js "^1.0.3"
minimalistic-assert "^1.0.0"
minimalistic-crypto-utils "^1.0.1"
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
hoist-non-react-statics@^2.3.1:
version "2.5.5"
resolved "https://registry.yarnpkg.com/hoist-non-react-statics/-/hoist-non-react-statics-2.5.5.tgz#c5903cf409c0dfd908f388e619d86b9c1174cb47"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-rqcy4pJo55FTTLWt+bU8ukscqHeE/e9KWvsOW2b/a3afxQZhwkQdT1rPPCJ0rYXdj4vNcasY8zHTH+jF/qStxw==
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +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
homedir-polyfill@^1.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/homedir-polyfill/-/homedir-polyfill-1.0.3.tgz#743298cef4e5af3e194161fbadcc2151d3a058e8"
integrity sha512-eSmmWE5bZTK2Nou4g0AI3zZ9rswp7GRKoKXS1BLUkvPviOqs4YTN1djQIqrXy9k5gEtdLPy86JjRwsNM9tnDcA==
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:
parse-passwd "^1.0.0"
hosted-git-info@^2.1.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.7.1"
resolved "https://registry.yarnpkg.com/hosted-git-info/-/hosted-git-info-2.7.1.tgz#97f236977bd6e125408930ff6de3eec6281ec047"
integrity sha512-7T/BxH19zbcCTa8XkMlbK5lTo1WtgkFi3GvdWEyNuc4Vex7/9Dqbnpsf4JMydcfj9HCg4zUWFTL3Za6lapg5/w==
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
hpack.js@^2.1.6:
version "2.1.6"
resolved "https://registry.yarnpkg.com/hpack.js/-/hpack.js-2.1.6.tgz#87774c0949e513f42e84575b3c45681fade2a0b2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-h3dMCUnlE/QuhFdbPEVoH63ioLI=
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:
inherits "^2.0.1"
obuf "^1.0.0"
readable-stream "^2.0.1"
wbuf "^1.1.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
html-element-map@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/html-element-map/-/html-element-map-1.0.1.tgz#3c4fcb4874ebddfe4283b51c8994e7713782b592"
integrity sha512-BZSfdEm6n706/lBfXKWa4frZRZcT5k1cOusw95ijZsHlI+GdgY0v95h6IzO3iIDf2ROwq570YTwqNPqHcNMozw==
dependencies:
array-filter "^1.0.0"
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
html-encoding-sniffer@^1.0.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
version "1.0.2"
resolved "https://registry.yarnpkg.com/html-encoding-sniffer/-/html-encoding-sniffer-1.0.2.tgz#e70d84b94da53aa375e11fe3a351be6642ca46f8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-71lZziiDnsuabfdYiUeWdCVyKuqwWi23L8YeIgV9jSSZHCtb6wB1BKWooH7L3tn4/FuZJMVWyNaIDr4RGmaSYw==
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:
whatwg-encoding "^1.0.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
html-entities@^1.2.1:
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
version "1.2.1"
resolved "https://registry.yarnpkg.com/html-entities/-/html-entities-1.2.1.tgz#0df29351f0721163515dfb9e5543e5f6eed5162f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-DfKTUfByEWNRXfueVUPl9u7VFi8=
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
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
html-to-react@^1.3.4:
version "1.3.4"
resolved "https://registry.yarnpkg.com/html-to-react/-/html-to-react-1.3.4.tgz#647b3a54fdec73a6461864b129fb0d1eec7d4589"
integrity sha512-/tWDdb/8Koi/QEP5YUY1653PcDpBnnMblXRhotnTuhFDjI1Fc6Wzox5d4sw73Xk5rM2OdM5np4AYjT/US/Wj7Q==
dependencies:
domhandler "^2.4.2"
escape-string-regexp "^1.0.5"
htmlparser2 "^3.10.0"
lodash.camelcase "^4.3.0"
ramda "^0.26"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
htmlparser2@^3.10.0, htmlparser2@^3.9.1:
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
version "3.10.1"
resolved "https://registry.yarnpkg.com/htmlparser2/-/htmlparser2-3.10.1.tgz#bd679dc3f59897b6a34bb10749c855bb53a9392f"
integrity sha512-IgieNijUMbkDovyoKObU1DUhm1iwNYE/fuifEoEHfd1oZKZDaONBSkal7Y01shxsM49R4XaMdGez3WnF9UfiCQ==
dependencies:
domelementtype "^1.3.1"
domhandler "^2.3.0"
domutils "^1.5.1"
entities "^1.1.1"
inherits "^2.0.1"
readable-stream "^3.1.1"
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
http-deceiver@^1.2.7:
version "1.2.7"
resolved "https://registry.yarnpkg.com/http-deceiver/-/http-deceiver-1.2.7.tgz#fa7168944ab9a519d337cb0bec7284dc3e723d87"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-+nFolEq5pRnTN8sL7HKE3D5yPYc=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
http-errors@1.7.2:
version "1.7.2"
resolved "https://registry.yarnpkg.com/http-errors/-/http-errors-1.7.2.tgz#4f5029cf13239f31036e5b2e55292bcfbcc85c8f"
integrity sha512-uUQBt3H/cSIVfch6i1EuPNy/YsRSOUBXTVfZ+yR7Zjez3qjBz6i9+i4zjNaoqcoFVI4lQJ5plg63TvGfRSDCRg==
dependencies:
depd "~1.1.2"
inherits "2.0.3"
setprototypeof "1.1.1"
statuses ">= 1.5.0 < 2"
toidentifier "1.0.0"
http-errors@~1.6.2:
version "1.6.3"
resolved "https://registry.yarnpkg.com/http-errors/-/http-errors-1.6.3.tgz#8b55680bb4be283a0b5bf4ea2e38580be1d9320d"
integrity sha1-i1VoC7S+KDoLW/TqLjhYC+HZMg0=
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
depd "~1.1.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
inherits "2.0.3"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
setprototypeof "1.1.0"
statuses ">= 1.4.0 < 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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
http-errors@~1.7.2:
version "1.7.3"
resolved "https://registry.yarnpkg.com/http-errors/-/http-errors-1.7.3.tgz#6c619e4f9c60308c38519498c14fbb10aacebb06"
integrity sha512-ZTTX0MWrsQ2ZAhA1cejAwDLycFsd7I7nVtnkT3Ol0aqodaKW+0CTZDQ1uBv5whptCnc8e8HeRRJxRs0kmm/Qfw==
dependencies:
depd "~1.1.2"
inherits "2.0.4"
setprototypeof "1.1.1"
statuses ">= 1.5.0 < 2"
toidentifier "1.0.0"
"http-parser-js@>=0.4.0 <0.4.11":
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
version "0.4.10"
resolved "https://registry.yarnpkg.com/http-parser-js/-/http-parser-js-0.4.10.tgz#92c9c1374c35085f75db359ec56cc257cbb93fa4"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-ksnBN0w1CF912zWexWzCV8u5P6Q=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
http-proxy-middleware@^0.19.1:
version "0.19.1"
resolved "https://registry.yarnpkg.com/http-proxy-middleware/-/http-proxy-middleware-0.19.1.tgz#183c7dc4aa1479150306498c210cdaf96080a43a"
integrity sha512-yHYTgWMQO8VvwNS22eLLloAkvungsKdKTLO8AJlftYIKNfJr3GK3zK0ZCfzDDGUBttdGc8xFy1mCitvNKQtC3Q==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
http-proxy "^1.17.0"
is-glob "^4.0.0"
lodash "^4.17.11"
micromatch "^3.1.10"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
http-proxy@^1.17.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.17.0"
resolved "https://registry.yarnpkg.com/http-proxy/-/http-proxy-1.17.0.tgz#7ad38494658f84605e2f6db4436df410f4e5be9a"
integrity sha512-Taqn+3nNvYRfJ3bGvKfBSRwy1v6eePlm3oc/aWVxZp57DQr5Eq3xhKJi7Z4hZpS8PC3H4qI+Yly5EmFacGuA/g==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
eventemitter3 "^3.0.0"
follow-redirects "^1.0.0"
requires-port "^1.0.0"
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
http-signature@~1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/http-signature/-/http-signature-1.2.0.tgz#9aecd925114772f3d95b65a60abb8f7c18fbace1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-muzZJRFHcvPZW2WmCruPfBj7rOE=
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:
assert-plus "^1.0.0"
jsprim "^1.2.2"
sshpk "^1.7.0"
https-browserify@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/https-browserify/-/https-browserify-1.0.0.tgz#ec06c10e0a34c0f2faf199f7fd7fc78fffd03c73"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-7AbBDgo0wPL68Zn3/X/Hj//QPHM=
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
Add style support to the artifacts app Test Plan: Note that the header, when rendered, is magenta. wchargin-branch: stylish-artifacts
2018-03-19 22:31:08 +00:00
hyphenate-style-name@^1.0.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/hyphenate-style-name/-/hyphenate-style-name-1.0.3.tgz#097bb7fa0b8f1a9cf0bd5c734cf95899981a9b48"
integrity sha512-EcuixamT82oplpoJ2XU4pDtKGWQ7b00CD9f1ug9IaQ3p1bkHMiKCZ9ut9QDI6qsa6cpUuB+A/I+zLtdNK4n2DQ==
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
iconv-lite@0.4.24, iconv-lite@^0.4.17, iconv-lite@^0.4.24, iconv-lite@^0.4.4, iconv-lite@~0.4.13:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "0.4.24"
resolved "https://registry.yarnpkg.com/iconv-lite/-/iconv-lite-0.4.24.tgz#2022b4b25fbddc21d2f524974a474aafe733908b"
integrity sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
safer-buffer ">= 2.1.2 < 3"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
icss-utils@^4.0.0, icss-utils@^4.1.1:
version "4.1.1"
resolved "https://registry.yarnpkg.com/icss-utils/-/icss-utils-4.1.1.tgz#21170b53789ee27447c2f47dd683081403f9a467"
integrity sha512-4aFq7wvWyMHKgxsH8QQtGpvbASCf+eM3wPRLI6R+MgAnTCZ6STYsRvttLvRWK0Nfif5piF394St3HeJDaljGPA==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
postcss "^7.0.14"
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
ieee754@^1.1.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.13"
resolved "https://registry.yarnpkg.com/ieee754/-/ieee754-1.1.13.tgz#ec168558e95aa181fd87d37f55c32bbcb6708b84"
integrity sha512-4vf7I2LYV/HaWerSo3XmlMkp5eZ83i+/CDluXi/IGTs/O1sejBNhTtnxzmRZfvOUqj7lZjqHkeTvpgSFDlWZTg==
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
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
iferr@^0.1.5:
version "0.1.5"
resolved "https://registry.yarnpkg.com/iferr/-/iferr-0.1.5.tgz#c60eed69e6d8fdb6b3104a1fcbca1c192dc5b501"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-xg7taebY/bazEEofy8ocGS3FtQE=
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
ignore-walk@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/ignore-walk/-/ignore-walk-3.0.1.tgz#a83e62e7d272ac0e3b551aaa82831a19b69f82f8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-DTVlMx3IYPe0/JJcYP7Gxg7ttZZu3IInhuEhbchuqneY9wWe5Ojy2mXLBaQFUQmo0AW2r3qG7m1mg86js+gnlQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
minimatch "^3.0.4"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
ignore@^3.3.5:
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
version "3.3.10"
resolved "https://registry.yarnpkg.com/ignore/-/ignore-3.3.10.tgz#0a97fb876986e8081c631160f8f9f389157f0043"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-Pgs951kaMm5GXP7MOvxERINe3gsaVjUWFm+UZPSq9xYriQAksyhg0csnS0KXSNRD5NmNdapXEpjxG49+AKh/ug==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
ignore@^4.0.6:
version "4.0.6"
resolved "https://registry.yarnpkg.com/ignore/-/ignore-4.0.6.tgz#750e3db5862087b4737ebac8207ffd1ef27b25fc"
integrity sha512-cyFDKrqc/YdcWFniJhzI42+AzS+gNwmUzOSFcRCQYwySuBBBy/KjuxWLZ/FHEH6Moq1NizMOBWyTcv8O4OZIMg==
import-fresh@^3.0.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/import-fresh/-/import-fresh-3.1.0.tgz#6d33fa1dcef6df930fae003446f33415af905118"
integrity sha512-PpuksHKGt8rXfWEr9m9EHIpgyyaltBy8+eF6GJM0QCAxMgxCfucMF3mjecK2QsJr0amJW7gTqh5/wht0z2UhEQ==
dependencies:
parent-module "^1.0.0"
resolve-from "^4.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
import-local@2.0.0, import-local@^2.0.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "2.0.0"
resolved "https://registry.yarnpkg.com/import-local/-/import-local-2.0.0.tgz#55070be38a5993cf18ef6db7e961f5bee5c5a09d"
integrity sha512-b6s04m3O+s3CGSbqDIyP4R6aAwAeYlVq9+WUWep6iHa8ETRf9yei1U48C5MmfJmV9AiLYYBKPMq/W+/WRpQmCQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
pkg-dir "^3.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
resolve-cwd "^2.0.0"
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
imurmurhash@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/imurmurhash/-/imurmurhash-0.1.4.tgz#9218b9b2b928a238b13dc4fb6b6d576f231453ea"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-khi5srkoojixPcT7a21XbyMUU+o=
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
indexes-of@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/indexes-of/-/indexes-of-1.0.1.tgz#f30f716c8e2bd346c7b67d3df3915566a7c05607"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-8w9xbI4r00bHtn0985FVZqfAVgc=
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
inflight@^1.0.4:
version "1.0.6"
resolved "https://registry.yarnpkg.com/inflight/-/inflight-1.0.6.tgz#49bd6331d7d02d0c09bc910a1075ba8165b56df9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Sb1jMdfQLQwJvJEKEHW6gWW1bfk=
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:
once "^1.3.0"
wrappy "1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
inherits@2, inherits@2.0.4, inherits@^2.0.1, inherits@^2.0.3, inherits@~2.0.1, inherits@~2.0.3:
version "2.0.4"
resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.4.tgz#0fa2c64f932917c3433a0ded55363aae37416b7c"
integrity sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==
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
inherits@2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.1.tgz#b17d08d326b4423e568eff719f91b0b1cbdf69f1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-sX0I0ya0Qj5Wjv9xn5GwscvfafE=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
inherits@2.0.3:
version "2.0.3"
resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.3.tgz#633c2c83e3da42a502f52466022480f4208261de"
integrity sha1-Yzwsg+PaQqUC9SRmAiSA9CCCYd4=
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
ini@^1.3.4, ini@^1.3.5, ini@~1.3.0:
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
version "1.3.5"
resolved "https://registry.yarnpkg.com/ini/-/ini-1.3.5.tgz#eee25f56db1c9ec6085e0c22778083f596abf927"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-RZY5huIKCMRWDUqZlEi72f/lmXKMvuszcMBduliQ3nnWbx9X/ZBQO7DijMEYS9EhHBb2qacRUMtC7svLwe0lcw==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
inline-style-prefixer@^5.0.4:
version "5.1.0"
resolved "https://registry.yarnpkg.com/inline-style-prefixer/-/inline-style-prefixer-5.1.0.tgz#cb63195f9456dcda25cf59743e45c4d9815b0811"
integrity sha512-giteQHPMrApQOSjNSjteO5ZGSGMRf9gas14fRy2lg2buSc1nRnj6o6xuNds5cMTKrkncyrTu3gJn/yflFMVdmg==
Add style support to the artifacts app Test Plan: Note that the header, when rendered, is magenta. wchargin-branch: stylish-artifacts
2018-03-19 22:31:08 +00:00
dependencies:
css-in-js-utils "^2.0.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
inquirer@3.3.0:
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
version "3.3.0"
resolved "https://registry.yarnpkg.com/inquirer/-/inquirer-3.3.0.tgz#9dd2f2ad765dcab1ff0443b491442a20ba227dc9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-h+xtnyk4EwKvFWHrUYsWErEVR+igKtLdchu+o0Z1RL7VU/jVMFbYir2bp6bAj8efFNxWqHX0dIss6fJQ+/+qeQ==
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:
ansi-escapes "^3.0.0"
chalk "^2.0.0"
cli-cursor "^2.1.0"
cli-width "^2.0.0"
external-editor "^2.0.4"
figures "^2.0.0"
lodash "^4.3.0"
mute-stream "0.0.7"
run-async "^2.2.0"
rx-lite "^4.0.8"
rx-lite-aggregates "^4.0.8"
string-width "^2.1.0"
strip-ansi "^4.0.0"
through "^2.3.6"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
inquirer@^6.2.2:
version "6.4.1"
resolved "https://registry.yarnpkg.com/inquirer/-/inquirer-6.4.1.tgz#7bd9e5ab0567cd23b41b0180b68e0cfa82fc3c0b"
integrity sha512-/Jw+qPZx4EDYsaT6uz7F4GJRNFMRdKNeUZw3ZnKV8lyuUgz/YWRCSUAJMZSVhSq4Ec0R2oYnyi6b3d4JXcL5Nw==
dependencies:
ansi-escapes "^3.2.0"
chalk "^2.4.2"
cli-cursor "^2.1.0"
cli-width "^2.0.0"
external-editor "^3.0.3"
figures "^2.0.0"
lodash "^4.17.11"
mute-stream "0.0.7"
run-async "^2.2.0"
rxjs "^6.4.0"
string-width "^2.1.0"
strip-ansi "^5.1.0"
through "^2.3.6"
Update better-sqlite3 to v5 When we took a dep on better-sqlite3 in #836, we used a fork, because better-sqlite3 did not yet support private in-memory databases via the `:memory:` filepath. As of better-sqlite3 v5, this has been added to mainline, so we no longer need the fork. The v4->v5 transition involves some breaking changes. The only ones that affected us were two field renames, from `lastUpdateROWID` to `lastUpdateRowid`, and `returnsData` to `reader`. Test plan: After updating the field accesses, `yarn test --full` passes. For added safety, I also blew away cache, loaded a nontrivial repository, and verified that the full cred workflow still works. cc @wchargin
2019-07-04 16:48:34 +00:00
integer@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/integer/-/integer-2.1.0.tgz#29134ea2f7ba3362ed4dbe6bcca992b1f18ff276"
integrity sha512-vBtiSgrEiNocWvvZX1RVfeOKa2mCHLZQ2p9nkQkQZ/BvEiY+6CcUz0eyjvIiewjJoeNidzg2I+tpPJvpyspL1w==
deps: add `better-sqlite3` (#836) Summary: I selected this over the alternatives, `sqlite` and `sqlite3`, primarily because its README explicitly acknowledges that using asynchronous APIs for CPU-bound or serialized work units are worse than useless. To me, this is a sign that the maintainer has his head on straight. The many-fold performance increase over `sqlite` and `sqlite3` is nice to have, too. For now, we use my fork of the project, which includes a critical patch to support private in-memory databases via SQLite’s standard `:memory:` filepath. When this patch is merged upstream, we can move back to mainline. Test Plan: The following session demonstrates the basic API and validates that the install has completed successfully: ```js const Database = require("better-sqlite3"); const db = new Database("/tmp/irrelevant", {memory: true}); db.prepare("CREATE TABLE pythagorean_triples (x, y, z)").run(); const insert = db.prepare("INSERT INTO pythagorean_triples VALUES (?, ?, ?)"); const get = db.prepare( "SELECT rowid, x * x + y * y AS xxyy, z * z AS zz FROM pythagorean_triples" ); function print(x) { console.log(JSON.stringify(x)); } print(insert.run(3, 4, 5)); print(get.all()); print(insert.run(5, 12, 13)); print(get.all()); db.prepare("DELETE FROM pythagorean_triples").run(); print(get.all()); ``` It prints: ```js {"changes":1,"lastInsertROWID":1} [{"rowid":1,"xxyy":25,"zz":25}] {"changes":1,"lastInsertROWID":2} [{"rowid":1,"xxyy":25,"zz":25},{"rowid":2,"xxyy":169,"zz":169}] [] ``` wchargin-branch: dep-better-sqlite3
2018-09-14 01:20:10 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
internal-ip@^4.3.0:
version "4.3.0"
resolved "https://registry.yarnpkg.com/internal-ip/-/internal-ip-4.3.0.tgz#845452baad9d2ca3b69c635a137acb9a0dad0907"
integrity sha512-S1zBo1D6zcsyuC6PMmY5+55YMILQ9av8lotMx447Bq6SAgo/sDK6y6uUKmuYhW7eacnIhFfsPmCNYdDzsnnDCg==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
default-gateway "^4.2.0"
ipaddr.js "^1.9.0"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
interpret@1.2.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.2.0"
resolved "https://registry.yarnpkg.com/interpret/-/interpret-1.2.0.tgz#d5061a6224be58e8083985f5014d844359576296"
integrity sha512-mT34yGKMNceBQUoVn7iCDKDntA7SC6gycMAWzGx1z/CMCTV7b2AAtXlo3nRyHZ1FelRkQbQjprHSYGwzLtkVbw==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
invariant@^2.2.1, invariant@^2.2.2, invariant@^2.2.4:
Add react-router-dom This commit adds a npm and flow-typed dependency, with no functional change. Test plan: `yarn travis` passes.
2018-05-08 19:02:17 +00:00
version "2.2.4"
resolved "https://registry.yarnpkg.com/invariant/-/invariant-2.2.4.tgz#610f3c92c9359ce1db616e538008d23ff35158e6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-phJfQVBuaJM5raOpJjSfkiD6BpbCE4Ns//LaXl6wGYtUBY83nWS6Rf9tXm2e8VaK60JEjYldbPif/A2B1C2gNA==
Add react-router-dom This commit adds a npm and flow-typed dependency, with no functional change. Test plan: `yarn travis` passes.
2018-05-08 19:02:17 +00:00
dependencies:
loose-envify "^1.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
invert-kv@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/invert-kv/-/invert-kv-2.0.0.tgz#7393f5afa59ec9ff5f67a27620d11c226e3eec02"
integrity sha512-wPVv/y/QQ/Uiirj/vh3oP+1Ww+AWehmi1g5fFWGPF6IpCBCDVrhgHRMvrLfdYcwDh3QJbGXDW4JAuzxElLSqKA==
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
ip-regex@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/ip-regex/-/ip-regex-2.1.0.tgz#fa78bf5d2e6913c911ce9f819ee5146bb6d844e9"
integrity sha1-+ni/XS5pE8kRzp+BnuUUa7bYROk=
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
ip@^1.1.0, ip@^1.1.5:
version "1.1.5"
resolved "https://registry.yarnpkg.com/ip/-/ip-1.1.5.tgz#bdded70114290828c0a039e72ef25f5aaec4354a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-vd7XARQpCCjAoDnnLvJfWq7ENUo=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
ipaddr.js@1.9.0, ipaddr.js@^1.9.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.9.0"
resolved "https://registry.yarnpkg.com/ipaddr.js/-/ipaddr.js-1.9.0.tgz#37df74e430a0e47550fe54a2defe30d8acd95f65"
integrity sha512-M4Sjn6N/+O6/IXSJseKqHoFc+5FdGJ22sXqnjTpdZweHK64MzEPAyQZyEU3R/KRv2GLoa7nNtg/C2Ev6m7z+eA==
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
is-accessor-descriptor@^0.1.6:
version "0.1.6"
resolved "https://registry.yarnpkg.com/is-accessor-descriptor/-/is-accessor-descriptor-0.1.6.tgz#a9e12cb3ae8d876727eeef3843f8a0897b5c98d6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-qeEss66Nh2cn7u84Q/igiXtcmNY=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
kind-of "^3.0.2"
is-accessor-descriptor@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-accessor-descriptor/-/is-accessor-descriptor-1.0.0.tgz#169c2f6d3df1f992618072365c9b0ea1f6878656"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-m5hnHTkcVsPfqx3AKlyttIPb7J+XykHvJP2B9bZDjlhLIoEq4XoK64Vg7boZlVWYK6LUY94dYPEE7Lh0ZkZKcQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
kind-of "^6.0.0"
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
is-alphabetical@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/is-alphabetical/-/is-alphabetical-1.0.3.tgz#eb04cc47219a8895d8450ace4715abff2258a1f8"
integrity sha512-eEMa6MKpHFzw38eKm56iNNi6GJ7lf6aLLio7Kr23sJPAECscgRtZvOBYybejWDQ2bM949Y++61PY+udzj5QMLA==
is-alphanumerical@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/is-alphanumerical/-/is-alphanumerical-1.0.3.tgz#57ae21c374277b3defe0274c640a5704b8f6657c"
integrity sha512-A1IGAPO5AW9vSh7omxIlOGwIqEvpW/TA+DksVOPM5ODuxKlZS09+TEM1E3275lJqO2oJ38vDpeAL3DCIiHE6eA==
dependencies:
is-alphabetical "^1.0.0"
is-decimal "^1.0.0"
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
is-arrayish@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/is-arrayish/-/is-arrayish-0.2.1.tgz#77c99840527aa8ecb1a8ba697b80645a7a926a9d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-d8mYQFJ6qOyxqLppe4BkWnqSap0=
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
is-binary-path@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-binary-path/-/is-binary-path-1.0.1.tgz#75f16642b480f187a711c814161fd3a4a7655898"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-dfFmQrSA8YenEcgUFh/TpKdlWJg=
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:
binary-extensions "^1.0.0"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
is-boolean-object@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-boolean-object/-/is-boolean-object-1.0.0.tgz#98f8b28030684219a95f375cfbd88ce3405dff93"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-mPiygDBoQhmpXzdc+9iM40Bd/5M=
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
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
is-buffer@^1.1.4, is-buffer@^1.1.5:
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
version "1.1.6"
resolved "https://registry.yarnpkg.com/is-buffer/-/is-buffer-1.1.6.tgz#efaa2ea9daa0d7ab2ea13a97b2b8ad51fefbe8be"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-NcdALwpXkTm5Zvvbk7owOUSvVvBKDgKP5/ewfXEznmQFfs4ZRmanOeKBTjRVjka3QFoN6XJ+9F3USqfHqTaU5w==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
is-callable@^1.1.3, is-callable@^1.1.4:
version "1.1.4"
resolved "https://registry.yarnpkg.com/is-callable/-/is-callable-1.1.4.tgz#1e1adf219e1eeb684d691f9d6a05ff0d30a24d75"
integrity sha512-r5p9sxJjYnArLjObpjA4xu5EKI3CuKHkJXMhT7kwbpUyIFD1n5PMAsoPvWnvtZiNz7LjkYDRZhd7FlI0eMijEA==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
is-ci@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/is-ci/-/is-ci-2.0.0.tgz#6bc6334181810e04b5c22b3d589fdca55026404c"
integrity sha512-YfJT7rkpQB0updsdHLGWrvhBJfcfzNNawYDNIyQXJz0IViGf75O8EBPKSdvw2rF+LGCsX4FZ8tcr3b19LcZq4w==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
ci-info "^2.0.0"
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
is-data-descriptor@^0.1.4:
version "0.1.4"
resolved "https://registry.yarnpkg.com/is-data-descriptor/-/is-data-descriptor-0.1.4.tgz#0b5ee648388e2c860282e793f1856fec3f301b56"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-C17mSDiOLIYCgueT8YVv7D8wG1Y=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
kind-of "^3.0.2"
is-data-descriptor@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-data-descriptor/-/is-data-descriptor-1.0.0.tgz#d84876321d0e7add03990406abbbbd36ba9268c7"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-jbRXy1FmtAoCjQkVmIVYwuuqDFUbaOeDjmed1tOGPrsMhtJA4rD9tkgA0F1qJ3gRFRXcHYVkdeaP50Q5rE/jLQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
kind-of "^6.0.0"
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
is-date-object@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-date-object/-/is-date-object-1.0.1.tgz#9aa20eb6aeebbff77fbd33e74ca01b33581d3a16"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-mqIOtq7rv/d/vTPnTKAbM1gdOhY=
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
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
is-decimal@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/is-decimal/-/is-decimal-1.0.3.tgz#381068759b9dc807d8c0dc0bfbae2b68e1da48b7"
integrity sha512-bvLSwoDg2q6Gf+E2LEPiklHZxxiSi3XAh4Mav65mKqTfCO1HM3uBs24TjEH8iJX3bbDdLXKJXBTmGzuTUuAEjQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
is-descriptor@^0.1.0:
version "0.1.6"
resolved "https://registry.yarnpkg.com/is-descriptor/-/is-descriptor-0.1.6.tgz#366d8240dde487ca51823b1ab9f07a10a78251ca"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-avDYr0SB3DwO9zsMov0gKCESFYqCnE4hq/4z3TdUlukEy5t9C0YRq7HLrsN52NAcqXKaepeCD0n+B0arnVG3Hg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
is-accessor-descriptor "^0.1.6"
is-data-descriptor "^0.1.4"
kind-of "^5.0.0"
is-descriptor@^1.0.0, is-descriptor@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-descriptor/-/is-descriptor-1.0.2.tgz#3b159746a66604b04f8c81524ba365c5f14d86ec"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-2eis5WqQGV7peooDyLmNEPUrps9+SXX5c9pL3xEB+4e9HnGuDa7mB7kHxHw4CbqS9k1T2hOH3miL8n8WtiYVtg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
is-accessor-descriptor "^1.0.0"
is-data-descriptor "^1.0.0"
kind-of "^6.0.2"
is-extendable@^0.1.0, is-extendable@^0.1.1:
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
version "0.1.1"
resolved "https://registry.yarnpkg.com/is-extendable/-/is-extendable-0.1.1.tgz#62b110e289a471418e3ec36a617d472e301dfc89"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-YrEQ4omkcUGOPsNqYX1HLjAd/Ik=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
is-extendable@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/is-extendable/-/is-extendable-1.0.1.tgz#a7470f9e426733d81bd81e1155264e3a3507cab4"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-arnXMxT1hhoKo9k1LZdmlNyJdDDfy2v0fXjFlmok4+i8ul/6WlbVge9bhM74OpNPQPMGUToDtz+KXa1PneJxOA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
is-plain-object "^2.0.4"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
is-extglob@^2.1.0, is-extglob@^2.1.1:
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
version "2.1.1"
resolved "https://registry.yarnpkg.com/is-extglob/-/is-extglob-2.1.1.tgz#a88c02535791f02ed37c76a1b9ea9773c833f8c2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-qIwCU1eR8C7TfHahueqXc8gz+MI=
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
is-fullwidth-code-point@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-1.0.0.tgz#ef9e31386f031a7f0d643af82fde50c457ef00cb"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-754xOG8DGn8NZDr4L95QxFfvAMs=
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:
number-is-nan "^1.0.0"
is-fullwidth-code-point@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/is-fullwidth-code-point/-/is-fullwidth-code-point-2.0.0.tgz#a3b30a5c4f199183167aaab93beefae3ddfb654f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-o7MKXE8ZkYMWeqq5O+764937ZU8=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
is-generator-fn@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/is-generator-fn/-/is-generator-fn-2.1.0.tgz#7d140adc389aaf3011a8f2a2a4cfa6faadffb118"
integrity sha512-cTIB4yPYL/Grw0EaSzASzg6bBy9gqCofvWN8okThAYIxKJZC+udlRAmGbM0XLeniEJSs8uEgHPGuHSe1XsOLSQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
is-glob@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/is-glob/-/is-glob-3.1.0.tgz#7ba5ae24217804ac70707b96922567486cc3e84a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-e6WuJCF4BKxwcHuWkiVnSGzD6Eo=
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:
is-extglob "^2.1.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
is-glob@^4.0.0, is-glob@^4.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "4.0.1"
resolved "https://registry.yarnpkg.com/is-glob/-/is-glob-4.0.1.tgz#7567dbe9f2f5e2467bc77ab83c4a29482407a5dc"
integrity sha512-5G0tKtBTFImOqDnLB2hG6Bp2qcKEFduo4tZu9MT/H6NQv/ghhy30o55ufafxJ/LdH79LLs2Kfrn85TLKyA7BUg==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
is-extglob "^2.1.1"
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
is-hexadecimal@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/is-hexadecimal/-/is-hexadecimal-1.0.3.tgz#e8a426a69b6d31470d3a33a47bb825cda02506ee"
integrity sha512-zxQ9//Q3D/34poZf8fiy3m3XVpbQc7ren15iKqrTtLPwkPD/t3Scy9Imp63FujULGxuK0ZlCwoo5xNpktFgbOA==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
is-number-object@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/is-number-object/-/is-number-object-1.0.3.tgz#f265ab89a9f445034ef6aff15a8f00b00f551799"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-8mWrian0RQNO9q/xWo8AsA9VF5k=
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +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
is-number@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/is-number/-/is-number-3.0.0.tgz#24fd6201a4782cf50561c810276afc7d12d71195"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-JP1iAaR4LPUFYcgQJ2r8fRLXEZU=
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:
kind-of "^3.0.2"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
is-path-cwd@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/is-path-cwd/-/is-path-cwd-2.2.0.tgz#67d43b82664a7b5191fd9119127eb300048a9fdb"
integrity sha512-w942bTcih8fdJPJmQHFzkS76NEP8Kzzvmw92cXsazb8intwLqPibPPdXf4ANdKV3rYMuuQYGIWtvz9JilB3NFQ==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
is-path-in-cwd@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/is-path-in-cwd/-/is-path-in-cwd-2.1.0.tgz#bfe2dca26c69f397265a4009963602935a053acb"
integrity sha512-rNocXHgipO+rvnP6dk3zI20RpOtrAM/kzbB258Uw5BWr3TpXi861yzjo16Dn4hUox07iw5AyeMLHWsujkjzvRQ==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
is-path-inside "^2.1.0"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
is-path-inside@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/is-path-inside/-/is-path-inside-2.1.0.tgz#7c9810587d659a40d27bcdb4d5616eab059494b2"
integrity sha512-wiyhTzfDWsvwAW53OBWF5zuvaOGlZ6PwYxAbPVDhpm+gM09xKQGjBq/8uYN12aDvMxnAnq3dxTyoSoRNmg5YFg==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
path-is-inside "^1.0.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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
is-plain-obj@^1.1.0:
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
version "1.1.0"
resolved "https://registry.yarnpkg.com/is-plain-obj/-/is-plain-obj-1.1.0.tgz#71a50c8429dfca773c92a390a4a03b39fcd51d3e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-caUMhCnfync8kqOQpKA7OfzVHT4=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
is-plain-object@^2.0.3, is-plain-object@^2.0.4:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
version "2.0.4"
resolved "https://registry.yarnpkg.com/is-plain-object/-/is-plain-object-2.0.4.tgz#2c163b3fafb1b606d9d17928f05c2a1c38e07677"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
isobject "^3.0.1"
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
is-promise@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/is-promise/-/is-promise-2.1.0.tgz#79a2a9ece7f096e80f36d2b2f3bc16c1ff4bf3fa"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-eaKp7OfwlugPNtKy87wWwf9L8/o=
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
is-regex@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/is-regex/-/is-regex-1.0.4.tgz#5517489b547091b0930e095654ced25ee97e9491"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-VRdIm1RwkbCTDglWVM7SXul+lJE=
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:
has "^1.0.1"
is-root@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-root/-/is-root-1.0.0.tgz#07b6c233bc394cd9d02ba15c966bd6660d6342d5"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-B7bCM7w5TNnQK6FclmvWZg1jQtU=
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
Remove service workers entirely (#635) Summary: This is a follow-up to #514, wherein we disabled new service workers and instructed any existing service workers to self-destruct. (See that PR for the rationale.) This commit removes them from our codebase entirely, enabling us to slim down our build process and our build output. Test Plan: Running `yarn start` still works. Building the static site and exploring it works, too. wchargin-branch: remove-sw
2018-08-10 19:49:45 +00:00
is-stream@^1.0.1, is-stream@^1.1.0:
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
version "1.1.0"
resolved "https://registry.yarnpkg.com/is-stream/-/is-stream-1.1.0.tgz#12d4a3dd4e68e0b79ceb8dbc84173ae80d91ca44"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-EtSj3U5o4Lec6428hBc66A2RykQ=
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
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
is-string@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/is-string/-/is-string-1.0.4.tgz#cc3a9b69857d621e963725a24caeec873b826e64"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-zDqbaYV9Yh6WNyWiTK7shzuCbmQ=
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
is-subset@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/is-subset/-/is-subset-0.1.1.tgz#8a59117d932de1de00f245fcdd39ce43f1e939a6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-ilkRfZMt4d4A8kX83TnOQ/HpOaY=
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
is-symbol@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-symbol/-/is-symbol-1.0.2.tgz#a055f6ae57192caee329e7a860118b497a950f38"
integrity sha512-HS8bZ9ox60yCJLH9snBpIwv9pYUAkcuLhSA1oero1UB5y9aiQpRA8y2ex945AOtCZL1lJDeIk3G5LthswI46Lw==
dependencies:
has-symbols "^1.0.0"
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
is-typedarray@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/is-typedarray/-/is-typedarray-1.0.0.tgz#e479c80858df0c1b11ddda6940f96011fcda4a9a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-5HnICFjfDBsR3dppQPlgEfzaSpo=
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
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
is-whitespace-character@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/is-whitespace-character/-/is-whitespace-character-1.0.3.tgz#b3ad9546d916d7d3ffa78204bca0c26b56257fac"
integrity sha512-SNPgMLz9JzPccD3nPctcj8sZlX9DAMJSKH8bP7Z6bohCwuNgX8xbWr1eTAYXX9Vpi/aSn8Y1akL9WgM3t43YNQ==
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
is-windows@^1.0.1, is-windows@^1.0.2:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/is-windows/-/is-windows-1.0.2.tgz#d1850eb9791ecd18e6182ce12a30f396634bb19d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-eXK1UInq2bPmjyX6e3VHIzMLobc4J94i4AWn+Hpq3OU5KkrRC96OAcR3PRJ/pGu6m8TRnBHP9dkXQVsT/COVIA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
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
is-word-character@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/is-word-character/-/is-word-character-1.0.3.tgz#264d15541cbad0ba833d3992c34e6b40873b08aa"
integrity sha512-0wfcrFgOOOBdgRNT9H33xe6Zi6yhX/uoc4U8NBZGeQQB0ctU1dnlNTyL9JM2646bHDTpsDm1Brb3VPoCIMrd/A==
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
is-wsl@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/is-wsl/-/is-wsl-1.1.0.tgz#1f16e4aa22b04d1336b66188a66af3c600c3a66d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-HxbkqiKwTRM2tmGIpmrzxgDDpm0=
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
isarray@1.0.0, isarray@^1.0.0, isarray@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/isarray/-/isarray-1.0.0.tgz#bb935d48582cba168c06834957a54a3e07124f11"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=
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
isexe@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/isexe/-/isexe-2.0.0.tgz#e8fbf374dc556ff8947a10dcb0572d633f2cfa10"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-6PvzdNxVb/iUehDcsFctYz8s+hA=
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
isobject@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/isobject/-/isobject-2.1.0.tgz#f065561096a3f1da2ef46272f815c840d87e0c89"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-8GVWEJaj8dou9GJy+BXIQNh+DIk=
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:
isarray "1.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
isobject@^3.0.0, isobject@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/isobject/-/isobject-3.0.1.tgz#4e431e92b11a9731636aa1f9c8d1ccbcfdab78df"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-TkMekrEalzFjaqH5yNHMvP2reN8=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Use isomorphic-fetch instead of node-fetch Summary: Paired with @dandelionmane. Test Plan: ``` $ CI=true yarn test $ yarn backend $ GITHUB_TOKEN="<your_token>" src/plugins/github/fetchGitHubRepoTest.sh ``` wchargin-branch: isomorphic-fetch
2018-03-20 00:01:41 +00:00
isomorphic-fetch@^2.1.1, isomorphic-fetch@^2.2.1:
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
version "2.2.1"
resolved "https://registry.yarnpkg.com/isomorphic-fetch/-/isomorphic-fetch-2.2.1.tgz#611ae1acf14f5e81f729507472819fe9733558a9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-YRrhrPFPXoH3KVB0coGf6XM1WKk=
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:
node-fetch "^1.0.1"
whatwg-fetch ">=0.10.0"
isstream@~0.1.2:
version "0.1.2"
resolved "https://registry.yarnpkg.com/isstream/-/isstream-0.1.2.tgz#47e63f7af55afa6f92e1500e690eb8b8529c099a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-R+Y/evVa+m+S4VAOaQ64uFKcCZo=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
istanbul-lib-coverage@^2.0.2, istanbul-lib-coverage@^2.0.5:
version "2.0.5"
resolved "https://registry.yarnpkg.com/istanbul-lib-coverage/-/istanbul-lib-coverage-2.0.5.tgz#675f0ab69503fad4b1d849f736baaca803344f49"
integrity sha512-8aXznuEPCJvGnMSRft4udDRDtb1V3pkQkMMI5LI+6HuQz5oQ4J2UFn1H82raA3qJtyOLkkwVqICBQkjnGtn5mA==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
istanbul-lib-instrument@^3.0.1, istanbul-lib-instrument@^3.3.0:
version "3.3.0"
resolved "https://registry.yarnpkg.com/istanbul-lib-instrument/-/istanbul-lib-instrument-3.3.0.tgz#a5f63d91f0bbc0c3e479ef4c5de027335ec6d630"
integrity sha512-5nnIN4vo5xQZHdXno/YDXJ0G+I3dAm4XgzfSVTPLQpj/zAV2dV6Juy0yaf10/zrJOJeHoN3fraFe+XRq2bFVZA==
dependencies:
"@babel/generator" "^7.4.0"
"@babel/parser" "^7.4.3"
"@babel/template" "^7.4.0"
"@babel/traverse" "^7.4.3"
"@babel/types" "^7.4.0"
istanbul-lib-coverage "^2.0.5"
semver "^6.0.0"
istanbul-lib-report@^2.0.4:
version "2.0.8"
resolved "https://registry.yarnpkg.com/istanbul-lib-report/-/istanbul-lib-report-2.0.8.tgz#5a8113cd746d43c4889eba36ab10e7d50c9b4f33"
integrity sha512-fHBeG573EIihhAblwgxrSenp0Dby6tJMFR/HvlerBsrCTD5bkUuoNtn3gVh29ZCS824cGGBPn7Sg7cNk+2xUsQ==
dependencies:
istanbul-lib-coverage "^2.0.5"
make-dir "^2.1.0"
supports-color "^6.1.0"
istanbul-lib-source-maps@^3.0.1:
version "3.0.6"
resolved "https://registry.yarnpkg.com/istanbul-lib-source-maps/-/istanbul-lib-source-maps-3.0.6.tgz#284997c48211752ec486253da97e3879defba8c8"
integrity sha512-R47KzMtDJH6X4/YW9XTx+jrLnZnscW4VpNN+1PViSYTejLVPWv7oov+Duf8YQSPyVRUvueQqz1TcsC6mooZTXw==
dependencies:
debug "^4.1.1"
istanbul-lib-coverage "^2.0.5"
make-dir "^2.1.0"
rimraf "^2.6.3"
source-map "^0.6.1"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
istanbul-reports@^2.1.1:
version "2.2.6"
resolved "https://registry.yarnpkg.com/istanbul-reports/-/istanbul-reports-2.2.6.tgz#7b4f2660d82b29303a8fe6091f8ca4bf058da1af"
integrity sha512-SKi4rnMyLBKe0Jy2uUdx28h8oG7ph2PPuQPvIAh31d+Ci+lSiEu4C+h3oBPuJ9+mPKhOyW0M8gY4U5NM1WLeXA==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
handlebars "^4.1.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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-changed-files@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-changed-files/-/jest-changed-files-24.8.0.tgz#7e7eb21cf687587a85e50f3d249d1327e15b157b"
integrity sha512-qgANC1Yrivsq+UrLXsvJefBKVoCsKB0Hv+mBb6NMjjZ90wwxCDmU3hsCXBya30cH+LnPYjwgcU65i6yJ5Nfuug==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/types" "^24.8.0"
execa "^1.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
throat "^4.0.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-cli@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-cli/-/jest-cli-24.8.0.tgz#b075ac914492ed114fa338ade7362a301693e989"
integrity sha512-+p6J00jSMPQ116ZLlHJJvdf8wbjNbZdeSX9ptfHX06/MSNaXmKihQzx5vQcw0q2G6JsdVkUIdWbOWtSnaYs3yA==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/core" "^24.8.0"
"@jest/test-result" "^24.8.0"
"@jest/types" "^24.8.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
chalk "^2.0.1"
exit "^0.1.2"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
import-local "^2.0.0"
is-ci "^2.0.0"
jest-config "^24.8.0"
jest-util "^24.8.0"
jest-validate "^24.8.0"
prompts "^2.0.1"
realpath-native "^1.1.0"
yargs "^12.0.2"
jest-config@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-config/-/jest-config-24.8.0.tgz#77db3d265a6f726294687cbbccc36f8a76ee0f4f"
integrity sha512-Czl3Nn2uEzVGsOeaewGWoDPD8GStxCpAe0zOYs2x2l0fZAgPbCr3uwUkgNKV3LwE13VXythM946cd5rdGkkBZw==
dependencies:
"@babel/core" "^7.1.0"
"@jest/test-sequencer" "^24.8.0"
"@jest/types" "^24.8.0"
babel-jest "^24.8.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
chalk "^2.0.1"
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
glob "^7.1.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-environment-jsdom "^24.8.0"
jest-environment-node "^24.8.0"
jest-get-type "^24.8.0"
jest-jasmine2 "^24.8.0"
jest-regex-util "^24.3.0"
jest-resolve "^24.8.0"
jest-util "^24.8.0"
jest-validate "^24.8.0"
micromatch "^3.1.10"
pretty-format "^24.8.0"
realpath-native "^1.1.0"
jest-diff@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-diff/-/jest-diff-24.8.0.tgz#146435e7d1e3ffdf293d53ff97e193f1d1546172"
integrity sha512-wxetCEl49zUpJ/bvUmIFjd/o52J+yWcoc5ZyPq4/W1LUKGEhRYDIbP1KcF6t+PvqNrGAFk4/JhtxDq/Nnzs66g==
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:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
chalk "^2.0.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
diff-sequences "^24.3.0"
jest-get-type "^24.8.0"
pretty-format "^24.8.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-docblock@^24.3.0:
version "24.3.0"
resolved "https://registry.yarnpkg.com/jest-docblock/-/jest-docblock-24.3.0.tgz#b9c32dac70f72e4464520d2ba4aec02ab14db5dd"
integrity sha512-nlANmF9Yq1dufhFlKG9rasfQlrY7wINJbo3q01tu56Jv5eBU5jirylhF2O5ZBnLxzOVBGRDz/9NAwNyBtG4Nyg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
detect-newline "^2.1.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-each@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-each/-/jest-each-24.8.0.tgz#a05fd2bf94ddc0b1da66c6d13ec2457f35e52775"
integrity sha512-NrwK9gaL5+XgrgoCsd9svsoWdVkK4gnvyhcpzd6m487tXHqIdYeykgq3MKI1u4I+5Zf0tofr70at9dWJDeb+BA==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/types" "^24.8.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
chalk "^2.0.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-get-type "^24.8.0"
jest-util "^24.8.0"
pretty-format "^24.8.0"
jest-environment-jsdom@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-environment-jsdom/-/jest-environment-jsdom-24.8.0.tgz#300f6949a146cabe1c9357ad9e9ecf9f43f38857"
integrity sha512-qbvgLmR7PpwjoFjM/sbuqHJt/NCkviuq9vus9NBn/76hhSidO+Z6Bn9tU8friecegbJL8gzZQEMZBQlFWDCwAQ==
dependencies:
"@jest/environment" "^24.8.0"
"@jest/fake-timers" "^24.8.0"
"@jest/types" "^24.8.0"
jest-mock "^24.8.0"
jest-util "^24.8.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
jsdom "^11.5.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-environment-node@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-environment-node/-/jest-environment-node-24.8.0.tgz#d3f726ba8bc53087a60e7a84ca08883a4c892231"
integrity sha512-vIGUEScd1cdDgR6sqn2M08sJTRLQp6Dk/eIkCeO4PFHxZMOgy+uYLPMC4ix3PEfM5Au/x3uQ/5Tl0DpXXZsJ/Q==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/environment" "^24.8.0"
"@jest/fake-timers" "^24.8.0"
"@jest/types" "^24.8.0"
jest-mock "^24.8.0"
jest-util "^24.8.0"
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
jest-fetch-mock@^2.1.2:
version "2.1.2"
resolved "https://registry.yarnpkg.com/jest-fetch-mock/-/jest-fetch-mock-2.1.2.tgz#1260b347918e3931c4ec743ceaf60433da661bd0"
integrity sha512-tcSR4Lh2bWLe1+0w/IwvNxeDocMI/6yIA2bijZ0fyWxC4kQ18lckQ1n7Yd40NKuisGmcGBRFPandRXrW/ti/Bw==
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
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
cross-fetch "^2.2.2"
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
promise-polyfill "^7.1.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-get-type@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-get-type/-/jest-get-type-24.8.0.tgz#a7440de30b651f5a70ea3ed7ff073a32dfe646fc"
integrity sha512-RR4fo8jEmMD9zSz2nLbs2j0zvPpk/KCEz3a62jJWbd2ayNo0cb+KFRxPHVhE4ZmgGJEQp0fosmNz84IfqM8cMQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-haste-map@^24.8.0:
version "24.8.1"
resolved "https://registry.yarnpkg.com/jest-haste-map/-/jest-haste-map-24.8.1.tgz#f39cc1d2b1d907e014165b4bd5a957afcb992982"
integrity sha512-SwaxMGVdAZk3ernAx2Uv2sorA7jm3Kx+lR0grp6rMmnY06Kn/urtKx1LPN2mGTea4fCT38impYT28FfcLUhX0g==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/types" "^24.8.0"
anymatch "^2.0.0"
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
fb-watchman "^2.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
graceful-fs "^4.1.15"
Upgrade jest and typings (#893) Motivated by my desire for `.toMatchInlineSnapshot()`. Really we just need and updated typing file for this, but I upgraded `jest` too to just get us in a clean state. Commit generated via: ``` yarn add --dev jest flow-typed install jest@23.6.0 ``` Test plan: `yarn test`
2018-09-26 01:48:54 +00:00
invariant "^2.2.4"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-serializer "^24.4.0"
jest-util "^24.8.0"
jest-worker "^24.6.0"
micromatch "^3.1.10"
sane "^4.0.3"
walker "^1.0.7"
optionalDependencies:
fsevents "^1.2.7"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-jasmine2@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-jasmine2/-/jest-jasmine2-24.8.0.tgz#a9c7e14c83dd77d8b15e820549ce8987cc8cd898"
integrity sha512-cEky88npEE5LKd5jPpTdDCLvKkdyklnaRycBXL6GNmpxe41F0WN44+i7lpQKa/hcbXaQ+rc9RMaM4dsebrYong==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/traverse" "^7.1.0"
"@jest/environment" "^24.8.0"
"@jest/test-result" "^24.8.0"
"@jest/types" "^24.8.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
chalk "^2.0.1"
co "^4.6.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
expect "^24.8.0"
is-generator-fn "^2.0.0"
jest-each "^24.8.0"
jest-matcher-utils "^24.8.0"
jest-message-util "^24.8.0"
jest-runtime "^24.8.0"
jest-snapshot "^24.8.0"
jest-util "^24.8.0"
pretty-format "^24.8.0"
throat "^4.0.0"
jest-leak-detector@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-leak-detector/-/jest-leak-detector-24.8.0.tgz#c0086384e1f650c2d8348095df769f29b48e6980"
integrity sha512-cG0yRSK8A831LN8lIHxI3AblB40uhv0z+SsQdW3GoMMVcK+sJwrIIyax5tu3eHHNJ8Fu6IMDpnLda2jhn2pD/g==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
pretty-format "^24.8.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-matcher-utils@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-matcher-utils/-/jest-matcher-utils-24.8.0.tgz#2bce42204c9af12bde46f83dc839efe8be832495"
integrity sha512-lex1yASY51FvUuHgm0GOVj7DCYEouWSlIYmCW7APSqB9v8mXmKSn5+sWVF0MhuASG0bnYY106/49JU1FZNl5hw==
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:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
chalk "^2.0.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-diff "^24.8.0"
jest-get-type "^24.8.0"
pretty-format "^24.8.0"
jest-message-util@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-message-util/-/jest-message-util-24.8.0.tgz#0d6891e72a4beacc0292b638685df42e28d6218b"
integrity sha512-p2k71rf/b6ns8btdB0uVdljWo9h0ovpnEe05ZKWceQGfXYr4KkzgKo3PBi8wdnd9OtNh46VpNIJynUn/3MKm1g==
dependencies:
"@babel/code-frame" "^7.0.0"
"@jest/test-result" "^24.8.0"
"@jest/types" "^24.8.0"
"@types/stack-utils" "^1.0.1"
chalk "^2.0.1"
micromatch "^3.1.10"
slash "^2.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
stack-utils "^1.0.1"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-mock@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-mock/-/jest-mock-24.8.0.tgz#2f9d14d37699e863f1febf4e4d5a33b7fdbbde56"
integrity sha512-6kWugwjGjJw+ZkK4mDa0Df3sDlUTsV47MSrT0nGQ0RBWJbpODDQ8MHDVtGtUYBne3IwZUhtB7elxHspU79WH3A==
dependencies:
"@jest/types" "^24.8.0"
jest-pnp-resolver@^1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/jest-pnp-resolver/-/jest-pnp-resolver-1.2.1.tgz#ecdae604c077a7fbc70defb6d517c3c1c898923a"
integrity sha512-pgFw2tm54fzgYvc/OHrnysABEObZCUNFnhjoRjaVOCN8NYc032/gVjPaHD4Aq6ApkSieWtfKAFQtmDKAmhupnQ==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-regex-util@^24.3.0:
version "24.3.0"
resolved "https://registry.yarnpkg.com/jest-regex-util/-/jest-regex-util-24.3.0.tgz#d5a65f60be1ae3e310d5214a0307581995227b36"
integrity sha512-tXQR1NEOyGlfylyEjg1ImtScwMq8Oh3iJbGTjN7p0J23EuVX1MA8rwU69K4sLbCmwzgCUbVkm0FkSF9TdzOhtg==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-resolve-dependencies@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-resolve-dependencies/-/jest-resolve-dependencies-24.8.0.tgz#19eec3241f2045d3f990dba331d0d7526acff8e0"
integrity sha512-hyK1qfIf/krV+fSNyhyJeq3elVMhK9Eijlwy+j5jqmZ9QsxwKBiP6qukQxaHtK8k6zql/KYWwCTQ+fDGTIJauw==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/types" "^24.8.0"
jest-regex-util "^24.3.0"
jest-snapshot "^24.8.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-resolve@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-resolve/-/jest-resolve-24.8.0.tgz#84b8e5408c1f6a11539793e2b5feb1b6e722439f"
integrity sha512-+hjSzi1PoRvnuOICoYd5V/KpIQmkAsfjFO71458hQ2Whi/yf1GDeBOFj8Gxw4LrApHsVJvn5fmjcPdmoUHaVKw==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/types" "^24.8.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
browser-resolve "^1.11.3"
chalk "^2.0.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-pnp-resolver "^1.2.1"
realpath-native "^1.1.0"
jest-runner@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-runner/-/jest-runner-24.8.0.tgz#4f9ae07b767db27b740d7deffad0cf67ccb4c5bb"
integrity sha512-utFqC5BaA3JmznbissSs95X1ZF+d+4WuOWwpM9+Ak356YtMhHE/GXUondZdcyAAOTBEsRGAgH/0TwLzfI9h7ow==
dependencies:
"@jest/console" "^24.7.1"
"@jest/environment" "^24.8.0"
"@jest/test-result" "^24.8.0"
"@jest/types" "^24.8.0"
chalk "^2.4.2"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
exit "^0.1.2"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
graceful-fs "^4.1.15"
jest-config "^24.8.0"
jest-docblock "^24.3.0"
jest-haste-map "^24.8.0"
jest-jasmine2 "^24.8.0"
jest-leak-detector "^24.8.0"
jest-message-util "^24.8.0"
jest-resolve "^24.8.0"
jest-runtime "^24.8.0"
jest-util "^24.8.0"
jest-worker "^24.6.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
source-map-support "^0.5.6"
throat "^4.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-runtime@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-runtime/-/jest-runtime-24.8.0.tgz#05f94d5b05c21f6dc54e427cd2e4980923350620"
integrity sha512-Mq0aIXhvO/3bX44ccT+czU1/57IgOMyy80oM0XR/nyD5zgBcesF84BPabZi39pJVA6UXw+fY2Q1N+4BiVUBWOA==
dependencies:
"@jest/console" "^24.7.1"
"@jest/environment" "^24.8.0"
"@jest/source-map" "^24.3.0"
"@jest/transform" "^24.8.0"
"@jest/types" "^24.8.0"
"@types/yargs" "^12.0.2"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
chalk "^2.0.1"
exit "^0.1.2"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
glob "^7.1.3"
graceful-fs "^4.1.15"
jest-config "^24.8.0"
jest-haste-map "^24.8.0"
jest-message-util "^24.8.0"
jest-mock "^24.8.0"
jest-regex-util "^24.3.0"
jest-resolve "^24.8.0"
jest-snapshot "^24.8.0"
jest-util "^24.8.0"
jest-validate "^24.8.0"
realpath-native "^1.1.0"
slash "^2.0.0"
strip-bom "^3.0.0"
yargs "^12.0.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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-serializer@^24.4.0:
version "24.4.0"
resolved "https://registry.yarnpkg.com/jest-serializer/-/jest-serializer-24.4.0.tgz#f70c5918c8ea9235ccb1276d232e459080588db3"
integrity sha512-k//0DtglVstc1fv+GY/VHDIjrtNjdYvYjMlbLUed4kxrE92sIUewOi5Hj3vrpB8CXfkJntRPDRjCrCvUhBdL8Q==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-snapshot@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-snapshot/-/jest-snapshot-24.8.0.tgz#3bec6a59da2ff7bc7d097a853fb67f9d415cb7c6"
integrity sha512-5ehtWoc8oU9/cAPe6fez6QofVJLBKyqkY2+TlKTOf0VllBB/mqUNdARdcjlZrs9F1Cv+/HKoCS/BknT0+tmfPg==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@babel/types" "^7.0.0"
"@jest/types" "^24.8.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
chalk "^2.0.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
expect "^24.8.0"
jest-diff "^24.8.0"
jest-matcher-utils "^24.8.0"
jest-message-util "^24.8.0"
jest-resolve "^24.8.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
mkdirp "^0.5.1"
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
natural-compare "^1.4.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
pretty-format "^24.8.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
semver "^5.5.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-util@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-util/-/jest-util-24.8.0.tgz#41f0e945da11df44cc76d64ffb915d0716f46cd1"
integrity sha512-DYZeE+XyAnbNt0BG1OQqKy/4GVLPtzwGx5tsnDrFcax36rVE3lTA5fbvgmbVPUZf9w77AJ8otqR4VBbfFJkUZA==
dependencies:
"@jest/console" "^24.7.1"
"@jest/fake-timers" "^24.8.0"
"@jest/source-map" "^24.3.0"
"@jest/test-result" "^24.8.0"
"@jest/types" "^24.8.0"
callsites "^3.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
chalk "^2.0.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
graceful-fs "^4.1.15"
is-ci "^2.0.0"
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
mkdirp "^0.5.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
slash "^2.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
source-map "^0.6.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-validate@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-validate/-/jest-validate-24.8.0.tgz#624c41533e6dfe356ffadc6e2423a35c2d3b4849"
integrity sha512-+/N7VOEMW1Vzsrk3UWBDYTExTPwf68tavEPKDnJzrC6UlHtUDU/fuEdXqFoHzv9XnQ+zW6X3qMZhJ3YexfeLDA==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/types" "^24.8.0"
camelcase "^5.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
chalk "^2.0.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-get-type "^24.8.0"
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
leven "^2.1.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
pretty-format "^24.8.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-watcher@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest-watcher/-/jest-watcher-24.8.0.tgz#58d49915ceddd2de85e238f6213cef1c93715de4"
integrity sha512-SBjwHt5NedQoVu54M5GEx7cl7IGEFFznvd/HNT8ier7cCAx/Qgu9ZMlaTQkvK22G1YOpcWBLQPFSImmxdn3DAw==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/test-result" "^24.8.0"
"@jest/types" "^24.8.0"
"@types/yargs" "^12.0.9"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
ansi-escapes "^3.0.0"
chalk "^2.0.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-util "^24.8.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
string-length "^2.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest-worker@^24.6.0:
version "24.6.0"
resolved "https://registry.yarnpkg.com/jest-worker/-/jest-worker-24.6.0.tgz#7f81ceae34b7cde0c9827a6980c35b7cdc0161b3"
integrity sha512-jDwgW5W9qGNvpI1tNnvajh0a5IE/PuGLFmHk6aR/BZFz8tSgGw17GsDPXAJ6p91IvYDjOw8GpFbvvZGAK+DPQQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
merge-stream "^1.0.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
supports-color "^6.1.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jest@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/jest/-/jest-24.8.0.tgz#d5dff1984d0d1002196e9b7f12f75af1b2809081"
integrity sha512-o0HM90RKFRNWmAWvlyV8i5jGZ97pFwkeVoGvPW1EtLTgJc2+jcuqcbbqcSZLE/3f2S5pt0y2ZBETuhpWNl1Reg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
import-local "^2.0.0"
jest-cli "^24.8.0"
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
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
js-levenshtein@^1.1.3:
version "1.1.6"
resolved "https://registry.yarnpkg.com/js-levenshtein/-/js-levenshtein-1.1.6.tgz#c6cee58eb3550372df8deb85fad5ce66ce01d59d"
integrity sha512-X2BB11YZtrRqY4EnQcLX5Rh373zbK4alC1FW7D7MBhL2gtcC17cTnr6DmfHZeS0s2rTHjUTMMHfG7gO8SSdw+g==
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"js-tokens@^3.0.0 || ^4.0.0", js-tokens@^4.0.0:
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
version "4.0.0"
resolved "https://registry.yarnpkg.com/js-tokens/-/js-tokens-4.0.0.tgz#19203fb59991df98e3a287050d4647cdeaf32499"
integrity sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
js-tokens@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/js-tokens/-/js-tokens-3.0.2.tgz#9866df395102130e38f7f996bceb65443209c25b"
integrity sha1-mGbfOVECEw449/mWvOtlRDIJwls=
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
js-yaml@^3.13.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.13.1"
resolved "https://registry.yarnpkg.com/js-yaml/-/js-yaml-3.13.1.tgz#aff151b30bfdfa8e49e05da22e7415e9dfa37847"
integrity sha512-YfbcO7jXDdyj0DGxYVSlSeQNHbD7XPWvrVWeVUujrQEoZzWJIRrCPoyk6kL6IAjAG2IolMK4T0hNUe0HOUs5Jw==
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:
argparse "^1.0.7"
esprima "^4.0.0"
jsbn@~0.1.0:
version "0.1.1"
resolved "https://registry.yarnpkg.com/jsbn/-/jsbn-0.1.1.tgz#a5e654c2e5a2deb5f201d96cefbca80c0ef2f513"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-peZUwuWi3rXyAdls77yoDA7y9RM=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
jsdom@^11.5.1:
version "11.12.0"
resolved "https://registry.yarnpkg.com/jsdom/-/jsdom-11.12.0.tgz#1a80d40ddd378a1de59656e9e6dc5a3ba8657bc8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-y8Px43oyiBM13Zc1z780FrfNLJCXTL40EWlty/LXUtcjykRBNgLlCjWXpfSPBl2iv+N7koQN+dvqszHZgT/Fjw==
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:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
abab "^2.0.0"
acorn "^5.5.3"
acorn-globals "^4.1.0"
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
array-equal "^1.0.0"
cssom ">= 0.3.2 < 0.4.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
cssstyle "^1.0.0"
data-urls "^1.0.0"
domexception "^1.0.1"
escodegen "^1.9.1"
html-encoding-sniffer "^1.0.2"
left-pad "^1.3.0"
nwsapi "^2.0.7"
parse5 "4.0.0"
pn "^1.1.0"
request "^2.87.0"
request-promise-native "^1.0.5"
sax "^1.2.4"
symbol-tree "^3.2.2"
tough-cookie "^2.3.4"
w3c-hr-time "^1.0.1"
webidl-conversions "^4.0.2"
whatwg-encoding "^1.0.3"
whatwg-mimetype "^2.1.0"
whatwg-url "^6.4.1"
ws "^5.2.0"
xml-name-validator "^3.0.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
jsesc@^2.5.1:
version "2.5.2"
resolved "https://registry.yarnpkg.com/jsesc/-/jsesc-2.5.2.tgz#80564d2e483dacf6e8ef209650a67df3f0c283a4"
integrity sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA==
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
jsesc@~0.5.0:
version "0.5.0"
resolved "https://registry.yarnpkg.com/jsesc/-/jsesc-0.5.0.tgz#e7dee66e35d6fc16f710fe91d5cf69f70f08911d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-597mbjXW/Bb3EP6R1c9p9w8IkR0=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
json-parse-better-errors@^1.0.1, json-parse-better-errors@^1.0.2:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/json-parse-better-errors/-/json-parse-better-errors-1.0.2.tgz#bb867cfb3450e69107c131d1c514bab3dc8bcaa9"
integrity sha512-mrqyZKfX5EhL7hvqcV6WG1yYjnjeuYDzDhhcAAUrq8Po85NBQBJP+ZDUT75qZQ98IkUoBqdkExkukOU7Ts2wrw==
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
json-schema-traverse@^0.4.1:
version "0.4.1"
resolved "https://registry.yarnpkg.com/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz#69f6a87d9513ab8bb8fe63bdb0979c448e684660"
integrity sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==
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
json-schema@0.2.3:
version "0.2.3"
resolved "https://registry.yarnpkg.com/json-schema/-/json-schema-0.2.3.tgz#b480c892e59a2f05954ce727bd3f2a4e882f9e13"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-tIDIkuWaLwWVTOcnvT8qTogvnhM=
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
json-stable-stringify-without-jsonify@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz#9db7b59496ad3f3cfef30a75142d2d930ad72651"
integrity sha1-nbe1lJatPzz+8wp1FC0tkwrXJlE=
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
json-stable-stringify@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/json-stable-stringify/-/json-stable-stringify-1.0.1.tgz#9a759d39c5f2ff503fd5300646ed445f88c4f9af"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-mnWdOcXy/1A/1TAGRu1EX4jE+a8=
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:
jsonify "~0.0.0"
json-stringify-safe@~5.0.1:
version "5.0.1"
resolved "https://registry.yarnpkg.com/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz#1296a2d58fd45f19a0f6ce01d65701e2c735b6eb"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Epai1Y/UXxmg9s4B1lcB4sc1tus=
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
json3@^3.3.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.3.3"
resolved "https://registry.yarnpkg.com/json3/-/json3-3.3.3.tgz#7fc10e375fc5ae42c4705a5cc0aa6f62be305b81"
integrity sha512-c7/8mbUsKigAbLkD5B010BK4D9LZm7A1pNItkEwiUZRpIN66exu/e7YQWysGun+TRKaJp8MhemM+VkfWv42aCA==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
json5@^0.5.0:
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
version "0.5.1"
resolved "https://registry.yarnpkg.com/json5/-/json5-0.5.1.tgz#1eade7acc012034ad84e2396767ead9fa5495821"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Hq3nrMASA0rYTiOWdn6tn6VJWCE=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
json5@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/json5/-/json5-1.0.1.tgz#779fb0018604fa854eacbf6252180d83543e3dbe"
integrity sha512-aKS4WQjPenRxiQsC93MNfjx+nbF4PAdYzmd/1JIj8HYzqfbu86beTuNgXDzPknWk0n0uARlyewZo4s++ES36Ow==
dependencies:
minimist "^1.2.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
json5@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/json5/-/json5-2.1.0.tgz#e7a0c62c48285c628d20a10b85c89bb807c32850"
integrity sha512-8Mh9h6xViijj36g7Dxi+Y4S6hNGV96vcJZr/SrlHh1LR/pEn/8j/+qIBbs44YKl69Lrfctp4QD+AdWLTMqEZAQ==
dependencies:
minimist "^1.2.0"
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
jsonfile@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/jsonfile/-/jsonfile-4.0.0.tgz#8771aae0799b64076b76640fca058f9c10e33ecb"
integrity sha1-h3Gq4HmbZAdrdmQPygWPnBDjPss=
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
optionalDependencies:
graceful-fs "^4.1.6"
jsonify@~0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/jsonify/-/jsonify-0.0.0.tgz#2c74b6ee41d93ca51b7b5aaee8f503631d252a73"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-LHS27kHZPKUbe1qu6PUDYx0lKnM=
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
jsprim@^1.2.2:
version "1.4.1"
resolved "https://registry.yarnpkg.com/jsprim/-/jsprim-1.4.1.tgz#313e66bc1e5cc06e438bc1b7499c2e5c56acb6a2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-MT5mvB5cwG5Di8G3SZwuXFastqI=
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:
assert-plus "1.0.0"
extsprintf "1.3.0"
json-schema "0.2.3"
verror "1.10.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
jsx-ast-utils@^2.1.0, jsx-ast-utils@^2.2.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.2.1"
resolved "https://registry.yarnpkg.com/jsx-ast-utils/-/jsx-ast-utils-2.2.1.tgz#4d4973ebf8b9d2837ee91a8208cc66f3a2776cfb"
integrity sha512-v3FxCcAf20DayI+uxnCuw795+oOIkVu6EnJ1+kSzhqqTZHNkTZ7B66ZgLp4oLJ/gbA64cI0B7WRoHZMSRdyVRQ==
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:
array-includes "^3.0.3"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
object.assign "^4.1.0"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
killable@^1.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/killable/-/killable-1.0.1.tgz#4c8ce441187a061c7474fb87ca08e2a638194892"
integrity sha512-LzqtLKlUwirEUyl/nicirVmNiPvYs7l5n8wOPP7fyJVpUPkvCnW/vuiXGpylGUlnPDnB7311rARzAt3Mhswpjg==
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
kind-of@^3.0.2, kind-of@^3.0.3, kind-of@^3.2.0:
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
version "3.2.2"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-3.2.2.tgz#31ea21a734bab9bbb0f32466d893aea51e4a3c64"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-MeohpzS6ubuw8yRm2JOupR5KPGQ=
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:
is-buffer "^1.1.5"
kind-of@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-4.0.0.tgz#20813df3d712928b207378691a45066fae72dd57"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-IIE989cSkosgc3hpGkUGb65y3Vc=
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:
is-buffer "^1.1.5"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
kind-of@^5.0.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-5.1.0.tgz#729c91e2d857b7a419a1f9aa65685c4c33f5845d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-NGEErnH6F2vUuXDh+OlbcKW7/wOcfdRHaZ7VWtqCztfHri/++YKmP51OdWeGPuqCOba6kk2OTe5d02VmTB80Pw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
kind-of@^6.0.0, kind-of@^6.0.2:
version "6.0.2"
resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-6.0.2.tgz#01146b36a6218e64e58f3a8d66de5d7fc6f6d051"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-s5kLOcnH0XqDO+FvuaLX8DDjZ18CGFk7VygH40QoKPUQhW4e2rvM0rwUq0t8IQDOwYSeLK01U90OjzBTme2QqA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
kleur@^3.0.2:
version "3.0.3"
resolved "https://registry.yarnpkg.com/kleur/-/kleur-3.0.3.tgz#a79c9ecc86ee1ce3fa6206d1216c501f147fc07e"
integrity sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
lcid@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/lcid/-/lcid-2.0.0.tgz#6ef5d2df60e52f82eb228a4c373e8d1f397253cf"
integrity sha512-avPEb8P8EGnwXKClwsNUgryVjllcRqtMYa49NTsbQagYuT1DcXnl1915oxWjoyGrXR6zH/Y0Zc96xWsPcoDKeA==
dependencies:
invert-kv "^2.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
left-pad@^1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/left-pad/-/left-pad-1.3.0.tgz#5b8a3a7765dfe001261dde915589e782f8c94d1e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-XI5MPzVNApjAyhQzphX8BkmKsKUxD4LdyK24iZeQGinBN9yTQT3bFlCBy/aVx2HrNcqQGsdot8ghrjyrvMCoEA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
leven@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/leven/-/leven-2.1.0.tgz#c2e7a9f772094dee9d34202ae8acce4687875580"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-wuep93IJTe6dNCAq6KzORoeHVYA=
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
levn@^0.3.0, levn@~0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/levn/-/levn-0.3.0.tgz#3b09924edf9f083c0490fdd4c0bc4421e04764ee"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-OwmSTt+fCDwEkP3UwLxEIeBHZO4=
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:
prelude-ls "~1.1.2"
type-check "~0.3.2"
load-json-file@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/load-json-file/-/load-json-file-2.0.0.tgz#7947e42149af80d696cbf797bcaabcfe1fe29ca8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-eUfkIUmvgNaWy/eXvKq8/h/inKg=
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:
graceful-fs "^4.1.2"
parse-json "^2.2.0"
pify "^2.0.0"
strip-bom "^3.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
load-json-file@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/load-json-file/-/load-json-file-4.0.0.tgz#2f5f45ab91e33216234fd53adab668eb4ec0993b"
integrity sha1-L19Fq5HjMhYjT9U62rZo607AmTs=
dependencies:
graceful-fs "^4.1.2"
parse-json "^4.0.0"
pify "^3.0.0"
strip-bom "^3.0.0"
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
loader-runner@^2.3.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.4.0"
resolved "https://registry.yarnpkg.com/loader-runner/-/loader-runner-2.4.0.tgz#ed47066bfe534d7e84c4c7b9998c2a75607d9357"
integrity sha512-Jsmr89RcXGIwivFY21FcRrisYZfvLMTWx5kOLc+JTxtpBOG6xML0vzbc6SEQG2FO9/4Fc3wW4LVcB5DmGflaRw==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
loader-utils@1.1.0:
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
version "1.1.0"
resolved "https://registry.yarnpkg.com/loader-utils/-/loader-utils-1.1.0.tgz#c98aef488bcceda2ffb5e2de646d6a754429f5cd"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-yYrvSIvM7aL/teLeZG1qdUQp9c0=
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:
big.js "^3.1.3"
emojis-list "^2.0.0"
json5 "^0.5.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
loader-utils@1.2.3, loader-utils@^1.0.2, loader-utils@^1.1.0, loader-utils@^1.2.2, loader-utils@^1.2.3:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.2.3"
resolved "https://registry.yarnpkg.com/loader-utils/-/loader-utils-1.2.3.tgz#1ff5dc6911c9f0a062531a4c04b609406108c2c7"
integrity sha512-fkpz8ejdnEMG3s37wGL07iSBDg99O9D5yflE9RGNH3hRdx9SOwYfnGYdZOUIZitN8E+E2vkq3MUMYMvPYl5ZZA==
dependencies:
big.js "^5.2.2"
emojis-list "^2.0.0"
json5 "^1.0.1"
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
locate-path@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-2.0.0.tgz#2b568b265eec944c6d9c0de9c3dbbbca0354cd8e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-K1aLJl7slExtnA3pw9u7ygNUzY4=
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:
p-locate "^2.0.0"
path-exists "^3.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
locate-path@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/locate-path/-/locate-path-3.0.0.tgz#dbec3b3ab759758071b58fe59fc41871af21400e"
integrity sha512-7AO748wWnIhNqAuaty2ZWHkQHRSNfPVIsPIfwEOWO22AmaoVrWavlOcMR5nzTLNYvp36X220/maaRsrec1G65A==
dependencies:
p-locate "^3.0.0"
path-exists "^3.0.0"
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
lodash.assignin@^4.0.9:
version "4.2.0"
resolved "https://registry.yarnpkg.com/lodash.assignin/-/lodash.assignin-4.2.0.tgz#ba8df5fb841eb0a3e8044232b0e263a8dc6a28a2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-uo31+4QesKPoBEIysOJjqNxqKKI=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
lodash.bind@^4.1.4:
version "4.2.1"
resolved "https://registry.yarnpkg.com/lodash.bind/-/lodash.bind-4.2.1.tgz#7ae3017e939622ac31b7d7d7dcb1b34db1690d35"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-euMBfpOWIqwxt9fX3LGzTbFpDTU=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +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
lodash.camelcase@^4.3.0:
version "4.3.0"
resolved "https://registry.yarnpkg.com/lodash.camelcase/-/lodash.camelcase-4.3.0.tgz#b28aa6288a2b9fc651035c7711f65ab6190331a6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-soqmKIorn8ZRA1x3EfZathkDMaY=
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
Convert in-memory Git repos to cred graphs (#169) Test Plan: This snapshot test is too unwieldy to actually read—it’s 1000 lines of opaque SHAs and thrice-stringified JSON objects—so it should be interpreted as a regression test only. The programmatic tests should suffice. wchargin-branch: wip-git-create-graph
2018-04-30 22:23:37 +00:00
lodash.clonedeep@^4.5.0:
version "4.5.0"
resolved "https://registry.yarnpkg.com/lodash.clonedeep/-/lodash.clonedeep-4.5.0.tgz#e23f3f9c4f8fbdde872529c1071857a086e5ccef"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-4j8/nE+Pvd6HJSnBBxhXoIblzO8=
Convert in-memory Git repos to cred graphs (#169) Test Plan: This snapshot test is too unwieldy to actually read—it’s 1000 lines of opaque SHAs and thrice-stringified JSON objects—so it should be interpreted as a regression test only. The programmatic tests should suffice. wchargin-branch: wip-git-create-graph
2018-04-30 22:23:37 +00:00
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
lodash.debounce@^4.0.8:
version "4.0.8"
resolved "https://registry.yarnpkg.com/lodash.debounce/-/lodash.debounce-4.0.8.tgz#82d79bff30a67c4005ffd5e2515300ad9ca4d7af"
integrity sha1-gteb/zCmfEAF/9XiUVMArZyk168=
Remove service workers entirely (#635) Summary: This is a follow-up to #514, wherein we disabled new service workers and instructed any existing service workers to self-destruct. (See that PR for the rationale.) This commit removes them from our codebase entirely, enabling us to slim down our build process and our build output. Test Plan: Running `yarn start` still works. Building the static site and exploring it works, too. wchargin-branch: remove-sw
2018-08-10 19:49:45 +00:00
lodash.defaults@^4.0.1:
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
version "4.2.0"
resolved "https://registry.yarnpkg.com/lodash.defaults/-/lodash.defaults-4.2.0.tgz#d09178716ffea4dde9e5fb7b37f6f0802274580c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-0JF4cW/+pN3p5ft7N/bwgCJ0WAw=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
lodash.escape@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/lodash.escape/-/lodash.escape-4.0.1.tgz#c9044690c21e04294beaa517712fded1fa88de98"
integrity sha1-yQRGkMIeBClL6qUXcS/e0fqI3pg=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
lodash.filter@^4.4.0:
version "4.6.0"
resolved "https://registry.yarnpkg.com/lodash.filter/-/lodash.filter-4.6.0.tgz#668b1d4981603ae1cc5a6fa760143e480b4c4ace"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-ZosdSYFgOuHMWm+nYBQ+SAtMSs4=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
lodash.flatten@^4.2.0:
version "4.4.0"
resolved "https://registry.yarnpkg.com/lodash.flatten/-/lodash.flatten-4.4.0.tgz#f31c22225a9632d2bbf8e4addbef240aa765a61f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-8xwiIlqWMtK7+OSt2+8kCqdlph8=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
lodash.flattendeep@^4.4.0:
version "4.4.0"
resolved "https://registry.yarnpkg.com/lodash.flattendeep/-/lodash.flattendeep-4.4.0.tgz#fb030917f86a3134e5bc9bec0d69e0013ddfedb2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-+wMJF/hqMTTlvJvsDWngAT3f7bI=
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
lodash.foreach@^4.3.0:
version "4.5.0"
resolved "https://registry.yarnpkg.com/lodash.foreach/-/lodash.foreach-4.5.0.tgz#1a6a35eace401280c7f06dddec35165ab27e3e53"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Gmo16s5AEoDH8G3d7DUWWrJ+PlM=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
Add an equality function for `Graph` (#61) Summary: We need this for testing graph equality: deep-equality is not sufficient because two graphs can be logically equal even if, say, two nodes are added in different orders. This commit adds a dependency on `lodash.isequal` for deep equality. Test Plan: New unit tests added. Run `yarn flow && yarn test`. wchargin-branch: graph-equals
2018-03-03 05:13:30 +00:00
lodash.isequal@^4.5.0:
version "4.5.0"
resolved "https://registry.yarnpkg.com/lodash.isequal/-/lodash.isequal-4.5.0.tgz#415c4478f2bcc30120c22ce10ed3226f7d3e18e0"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-QVxEePK8wwEgwizhDtMib30+GOA=
Add an equality function for `Graph` (#61) Summary: We need this for testing graph equality: deep-equality is not sufficient because two graphs can be logically equal even if, say, two nodes are added in different orders. This commit adds a dependency on `lodash.isequal` for deep equality. Test Plan: New unit tests added. Run `yarn flow && yarn test`. wchargin-branch: graph-equals
2018-03-03 05:13:30 +00:00
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
lodash.map@^4.4.0:
version "4.6.0"
resolved "https://registry.yarnpkg.com/lodash.map/-/lodash.map-4.6.0.tgz#771ec7839e3473d9c4cde28b19394c3562f4f6d3"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-dx7Hg540c9nEzeKLGTlMNWL09tM=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
lodash.merge@^4.4.0:
Bump lodash.merge from 4.6.1 to 4.6.2 (#1213) Bumps [lodash.merge](https://github.com/lodash/lodash) from 4.6.1 to 4.6.2. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](https://github.com/lodash/lodash/commits) Signed-off-by: dependabot[bot] <support@github.com>
2019-07-11 00:03:01 +00:00
version "4.6.2"
resolved "https://registry.yarnpkg.com/lodash.merge/-/lodash.merge-4.6.2.tgz#558aa53b43b661e1925a0afdfa36a9a1085fe57a"
integrity sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
lodash.pick@^4.2.1:
version "4.4.0"
resolved "https://registry.yarnpkg.com/lodash.pick/-/lodash.pick-4.4.0.tgz#52f05610fff9ded422611441ed1fc123a03001b3"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-UvBWEP/53tQiYRRB7R/BI6AwAbM=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
lodash.reduce@^4.4.0:
version "4.6.0"
resolved "https://registry.yarnpkg.com/lodash.reduce/-/lodash.reduce-4.6.0.tgz#f1ab6b839299ad48f784abbf476596f03b914d3b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-8atrg5KZrUj3hKu/R2WW8DuRTTs=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
lodash.reject@^4.4.0:
version "4.6.0"
resolved "https://registry.yarnpkg.com/lodash.reject/-/lodash.reject-4.6.0.tgz#80d6492dc1470864bbf583533b651f42a9f52415"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-gNZJLcFHCGS79YNTO2UfQqn1JBU=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
lodash.some@^4.4.0:
version "4.6.0"
resolved "https://registry.yarnpkg.com/lodash.some/-/lodash.some-4.6.0.tgz#1bb9f314ef6b8baded13b549169b2a945eb68e4d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-G7nzFO9ri63tE7VJFpsqlF62jk0=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
Remove `address.sortedByAddress` (#161) Previously, the address module exported `sortedByAddress`, a utility function that sorts an array of `Addressable`s. This function was only used in test code. This commit replaces it with generic usage of `lodash.sortBy`. This reduces the API surface area of the module, and removes test-only code from the exported api. New dependency added: `lodash.sortby` https://www.npmjs.com/package/lodash.sortby
2018-04-27 21:29:49 +00:00
lodash.sortby@^4.7.0:
version "4.7.0"
resolved "https://registry.yarnpkg.com/lodash.sortby/-/lodash.sortby-4.7.0.tgz#edd14c824e2cc9c1e0b0a1b42bb5210516a42438"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-7dFMgk4sycHgsKG0K7UhBRakJDg=
Remove `address.sortedByAddress` (#161) Previously, the address module exported `sortedByAddress`, a utility function that sorts an array of `Addressable`s. This function was only used in test code. This commit replaces it with generic usage of `lodash.sortBy`. This reduces the API surface area of the module, and removes test-only code from the exported api. New dependency added: `lodash.sortby` https://www.npmjs.com/package/lodash.sortby
2018-04-27 21:29:49 +00:00
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
lodash.throttle@^4.1.1:
version "4.1.1"
resolved "https://registry.yarnpkg.com/lodash.throttle/-/lodash.throttle-4.1.1.tgz#c23e91b710242ac70c37f1e1cda9274cc39bf2f4"
integrity sha1-wj6RtxAkKscMN/HhzaknTMOb8vQ=
"lodash@>=3.5 <5", lodash@^4.15.0, lodash@^4.17.4, lodash@^4.3.0:
version "4.17.5"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.5.tgz#99a92d65c0272debe8c96b6057bc8fbfa3bed511"
integrity sha512-svL3uiZf1RwhH+cWrfZn3A4+U58wbP0tGVTLQPbjplZxZ8ROD9VLuNgsRniTlLe7OlSqR79RUehXgpBW/s0IQw==
lodash@^4.0.0, lodash@^4.17.11, lodash@^4.17.5, lodash@~4.17.4:
Port skeleton of Odyssey frontend (#1132) This commit integrates an bare skeleton of the odyssey frontend that we implemented in the [odyssey-hackathon] repository. You can see the working frontend that we are trying to port over at [sourcecred.io/odyssey-hackathon/][scio]. The prototype in the other repository has some tooling choices which are incompatible/redundant with decisions in our codebase (sass vs aphrodite), and requires some tools not yet present here (svg-react-loader). This commit includes the build and integration work needed to port the prototype frontend into mainline SourceCred. The frontend scaffold isn't yet integrated with any "real" Odyssey data. One potential issue: right now, every page that is rendered from the SourceCred homepage is contained within a [homepage/Page], meaning that it has full SourceCred website styling, along with the SourceCred website header. The [application][scio] also has a header. Currently, I work around this by having the Odyssey UI cover up the base header (via absolute positioning), which works but is hacky. We can consider more principled solutions: - Finding a way to specify routes which aren't contained by [homepage/Page]; maybe by adding a new top-level route [here][route-alternative]. - Unify the headers for the Odyssey viewer and the page as a whole (sounds like inappropriate entanglement?) - Have a website header and also an application header (sounds ugly?) [homepage/Page]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/Page.js [route-alternative]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/createRoutes.js#L17 Test plan: Run `yarn start`, and then navigate to `localhost:8080/odyssey/`. observe that a working website is displayed, and that the cred logo next to the word "SourceCred" is loaded properly (i.e. svg-react-loader is integrated properly). Observe that there are no build/compile errors from either `yarn start` or `yarn build`. Also, observe that the UI looks passably nice, and that if the number of elements in the entity lists is larger than can be displayed, the sidebar pane scrolls independently. The UI was tested in both Chrome and Firefox. [odyssey-hackathon]: https://github.com/sourcecred/odyssey-hackathon [scio]: https://sourcecred.io/odyssey-hackathon/ Thanks to @jmnemo, as the implementation is based on [his work]. [his work]: https://github.com/jmnemo/hackathon-event/
2019-05-06 15:15:39 +00:00
version "4.17.11"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.11.tgz#b39ea6229ef607ecd89e2c8df12536891cac9b8d"
integrity sha512-cQKh8igo5QUhZ7lg38DYWAxMvjSAKG0A8wGSVimP07SIUEK2UO+arSRKbRZWtelMtN5V0Hkwh5ryOto/SshYIg==
update lockfile Greenkeeper is updating our package.json, but not our lockfile. I should fix this. Test plan: Commit generated by running `yarn`
2019-07-19 10:50:31 +00:00
lodash@^4.17.13:
version "4.17.15"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.15.tgz#b447f6670a0455bbfeedd11392eff330ea097548"
integrity sha512-8xOcRHvCjnocdS5cpwXQXVzmmh5e5+saE2QGoeQmbKmRS6J3VQppPOIt0MnmE+4xlZoumy0GPG0D0MVIQbNA1A==
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
loglevel@^1.6.3:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.6.3"
resolved "https://registry.yarnpkg.com/loglevel/-/loglevel-1.6.3.tgz#77f2eb64be55a404c9fd04ad16d57c1d6d6b1280"
integrity sha512-LoEDv5pgpvWgPF4kNYuIp0qqSJVWak/dML0RY74xlzMZiT9w77teNAwKYKWBTYjlokMirg+o3jBwp+vlLrcfAA==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
loose-envify@^1.0.0, loose-envify@^1.1.0, loose-envify@^1.2.0, loose-envify@^1.3.1, loose-envify@^1.4.0:
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
version "1.4.0"
resolved "https://registry.yarnpkg.com/loose-envify/-/loose-envify-1.4.0.tgz#71ee51fa7be4caec1a63839f7e682d8132d30caf"
integrity sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q==
dependencies:
js-tokens "^3.0.0 || ^4.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
lru-cache@^4.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "4.1.5"
resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-4.1.5.tgz#8bbe50ea85bed59bc9e33dcab8235ee9bcf443cd"
integrity sha512-sWZlbEP2OsHNkXrMl5GYk/jKk70MBng6UU4YI/qGDYbgf6YbP4EvmqISbXCoJiRKs+1bSpFHVgQxvJ17F2li5g==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
pseudomap "^1.0.2"
yallist "^2.1.2"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
lru-cache@^5.1.1:
version "5.1.1"
resolved "https://registry.yarnpkg.com/lru-cache/-/lru-cache-5.1.1.tgz#1da27e6710271947695daf6848e847f01d84b920"
integrity sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
yallist "^3.0.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
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
make-dir@^2.0.0, make-dir@^2.1.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "2.1.0"
resolved "https://registry.yarnpkg.com/make-dir/-/make-dir-2.1.0.tgz#5f0310e18b8be898cc07009295a30ae41e91e6f5"
integrity sha512-LS9X+dc8KLxXCb8dni79fLIIUA5VyZoyjSMCwTluaXA0o27cCK0bhXkpgw+sTXVpPy/lSO57ilRixqk0vDmtRA==
dependencies:
pify "^4.0.1"
semver "^5.6.0"
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
makeerror@1.0.x:
version "1.0.11"
resolved "https://registry.yarnpkg.com/makeerror/-/makeerror-1.0.11.tgz#e01a5c9109f2af79660e4e8b9587790184f5a96c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-4BpckQnyr3lmDk6LlYd5AYT1qWw=
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:
tmpl "1.0.x"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
mamacro@^0.0.3:
version "0.0.3"
resolved "https://registry.yarnpkg.com/mamacro/-/mamacro-0.0.3.tgz#ad2c9576197c9f1abf308d0787865bd975a3f3e4"
integrity sha512-qMEwh+UujcQ+kbz3T6V+wAmO2U8veoq2w+3wY8MquqwVA3jChfwY+Tk52GZKDfACEPjuZ7r2oJLejwpt8jtwTA==
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
map-age-cleaner@^0.1.1:
version "0.1.3"
resolved "https://registry.yarnpkg.com/map-age-cleaner/-/map-age-cleaner-0.1.3.tgz#7d583a7306434c055fe474b0f45078e6e1b4b92a"
integrity sha512-bJzx6nMoP6PDLPBFmg7+xRKeFZvFboMrGlxmNj9ClvX53KrmvM5bXFXEWjbz4cz1AFn+jWJ9z/DJSz7hrs0w3w==
dependencies:
p-defer "^1.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
map-cache@^0.2.2:
version "0.2.2"
resolved "https://registry.yarnpkg.com/map-cache/-/map-cache-0.2.2.tgz#c32abd0bd6525d9b051645bb4f26ac5dc98a0dbf"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-wyq9C9ZSXZsFFkW7TyasXcmKDb8=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
map-visit@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/map-visit/-/map-visit-1.0.0.tgz#ecdca8f13144e660f1b5bd41f12f3479d98dfb8f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-7Nyo8TFE5mDxtb1B8S80edmN+48=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
object-visit "^1.0.0"
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
markdown-escapes@^1.0.0:
version "1.0.3"
resolved "https://registry.yarnpkg.com/markdown-escapes/-/markdown-escapes-1.0.3.tgz#6155e10416efaafab665d466ce598216375195f5"
integrity sha512-XUi5HJhhV5R74k8/0H2oCbCiYf/u4cO/rX8tnGkRvrqhsr5BRNU6Mg0yt/8UIx1iIS8220BNJsDb7XnILhLepw==
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
math-expression-evaluator@^1.2.14:
version "1.2.17"
resolved "https://registry.yarnpkg.com/math-expression-evaluator/-/math-expression-evaluator-1.2.17.tgz#de819fdbcd84dccd8fae59c6aeb79615b9d266ac"
integrity sha1-3oGf282E3M2PrlnGrreWFbnSZqw=
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
md5.js@^1.3.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.3.5"
resolved "https://registry.yarnpkg.com/md5.js/-/md5.js-1.3.5.tgz#b5d07b8e3216e3e27cd728d72f70d1e6a342005f"
integrity sha512-xitP+WxNPcTTOgnTJcrhM0xvdPepipPSf3I8EIpGKeFLjt3PlJLIDG3u8EX53ZIubkb+5U2+3rELYpEhHhzdkg==
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:
hash-base "^3.0.0"
inherits "^2.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
safe-buffer "^5.1.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
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
mdast-add-list-metadata@1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/mdast-add-list-metadata/-/mdast-add-list-metadata-1.0.1.tgz#95e73640ce2fc1fa2dcb7ec443d09e2bfe7db4cf"
integrity sha512-fB/VP4MJ0LaRsog7hGPxgOrSL3gE/2uEdZyDuSEnKCv/8IkYHiDkIQSbChiJoHyxZZXZ9bzckyRk+vNxFzh8rA==
dependencies:
unist-util-visit-parents "1.1.2"
Add dependency on `commonmark` (#440) Summary: We plan to use this to more intelligently extract references from GitHub text content. See #432. Test Plan: In a Node shell, running ```js const cm = require("commonmark"); var parser = new cm.Parser(); var ast = parser.parse("Hello\nworld"); var html = new cm.HtmlRenderer({softbreak: " "}).render(ast); console.log(html); ``` prints `<p>Hello world</p>`. wchargin-branch: commonmark
2018-06-29 00:01:31 +00:00
"mdurl@~ 1.0.1":
version "1.0.1"
resolved "https://registry.yarnpkg.com/mdurl/-/mdurl-1.0.1.tgz#fe85b2ec75a59037f2adfec100fd6c601761152e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-/oWy7HWlkDfyrf7BAP1sYBdhFS4=
Add dependency on `commonmark` (#440) Summary: We plan to use this to more intelligently extract references from GitHub text content. See #432. Test Plan: In a Node shell, running ```js const cm = require("commonmark"); var parser = new cm.Parser(); var ast = parser.parse("Hello\nworld"); var html = new cm.HtmlRenderer({softbreak: " "}).render(ast); console.log(html); ``` prints `<p>Hello world</p>`. wchargin-branch: commonmark
2018-06-29 00:01:31 +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
media-typer@0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/media-typer/-/media-typer-0.3.0.tgz#8710d7af0aa626f8fffa1ce00168545263255748"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-hxDXrwqmJvj/+hzgAWhUUmMlV0g=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
mem@^4.0.0:
version "4.3.0"
resolved "https://registry.yarnpkg.com/mem/-/mem-4.3.0.tgz#461af497bc4ae09608cdb2e60eefb69bff744178"
integrity sha512-qX2bG48pTqYRVmDB37rn/6PT7LcR8T7oAX3bf99u1Tt1nzxYfxkgqDwUwolPlXweM0XzBOBFzSx4kfp7KP1s/w==
dependencies:
map-age-cleaner "^0.1.1"
mimic-fn "^2.0.0"
p-is-promise "^2.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
memory-fs@^0.4.0, memory-fs@^0.4.1, memory-fs@~0.4.1:
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
version "0.4.1"
resolved "https://registry.yarnpkg.com/memory-fs/-/memory-fs-0.4.1.tgz#3a9a20b8462523e447cfbc7e8bb80ed667bfc552"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-OpoguEYlI+RHz7x+i7gO1me/xVI=
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:
errno "^0.1.3"
readable-stream "^2.0.1"
merge-descriptors@1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/merge-descriptors/-/merge-descriptors-1.0.1.tgz#b00aaa556dd8b44568150ec9d1b953f3f90cbb61"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-sAqqVW3YtEVoFQ7J0blT8/kMu2E=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
merge-stream@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/merge-stream/-/merge-stream-1.0.1.tgz#4041202d508a342ba00174008df0c251b8c135e1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-QEEgLVCKNCugAXQAjfDCUbjBNeE=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
readable-stream "^2.0.1"
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
methods@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/methods/-/methods-1.1.2.tgz#5529a4d67654134edcc5266656835b0f851afcee"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-VSmk1nZUE07cxSZmVoNbD4Ua/O4=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
micromatch@^3.0.4, micromatch@^3.1.10, micromatch@^3.1.4, micromatch@^3.1.8:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
version "3.1.10"
resolved "https://registry.yarnpkg.com/micromatch/-/micromatch-3.1.10.tgz#70859bc95c9840952f359a068a3fc49f9ecfac23"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-MWikgl9n9M3w+bpsY3He8L+w9eF9338xRl8IAO5viDizwSzziFEyUzo2xrrloB64ADbTf8uA8vRqqttDTOmccg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
arr-diff "^4.0.0"
array-unique "^0.3.2"
braces "^2.3.1"
define-property "^2.0.2"
extend-shallow "^3.0.2"
extglob "^2.0.4"
fragment-cache "^0.2.1"
kind-of "^6.0.2"
nanomatch "^1.2.9"
object.pick "^1.3.0"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.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
miller-rabin@^4.0.0:
version "4.0.1"
resolved "https://registry.yarnpkg.com/miller-rabin/-/miller-rabin-4.0.1.tgz#f080351c865b0dc562a8462966daa53543c78a4d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-115fLhvZVqWwHPbClyntxEVfVDfl9DLLTuJvq3g2O/Oxi8AiNouAHvDSzHS0viUJc+V5vm3eq91Xwqn9dp4jRA==
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:
bn.js "^4.0.0"
brorand "^1.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
mime-db@1.40.0, "mime-db@>= 1.40.0 < 2":
version "1.40.0"
resolved "https://registry.yarnpkg.com/mime-db/-/mime-db-1.40.0.tgz#a65057e998db090f732a68f6c276d387d4126c32"
integrity sha512-jYdeOMPy9vnxEqFRRo6ZvTZ8d9oPb+k18PKoYNYUe2stVEBPPwsln/qWzdbmaIvnhZ9v2P+CuecK+fpUfsV2mA==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
mime-types@^2.1.12, mime-types@~2.1.17, mime-types@~2.1.19, mime-types@~2.1.24:
version "2.1.24"
resolved "https://registry.yarnpkg.com/mime-types/-/mime-types-2.1.24.tgz#b6f8d0b3e951efb77dedeca194cff6d16f676f81"
integrity sha512-WaFHS3MCl5fapm3oLxU4eYDw77IQM2ACcxQ9RIxfaC3ooc6PFuBMGZZsYpvoXS5D5QTWPieo1jjLdAm3TBP3cQ==
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
mime-db "1.40.0"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
mime@1.6.0:
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
version "1.6.0"
resolved "https://registry.yarnpkg.com/mime/-/mime-1.6.0.tgz#32cd9e5c64553bd58d19a568af452acff04981b1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
mime@^2.4.2, mime@^2.4.4:
version "2.4.4"
resolved "https://registry.yarnpkg.com/mime/-/mime-2.4.4.tgz#bd7b91135fc6b01cde3e9bae33d659b63d8857e5"
integrity sha512-LRxmNwziLPT828z+4YkNzloCFC2YM4wrB99k+AV5ZbEyfGNWfG8SO1FUXLmLDBSo89NrJZ4DIWeLjy1CHGhMGA==
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
mimic-fn@^1.0.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/mimic-fn/-/mimic-fn-1.2.0.tgz#820c86a39334640e99516928bd03fca88057d022"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-jf84uxzwiuiIVKiOLpfYk7N46TSy8ubTonmneY9vrpHNAnp0QBt2BxWV9dO3/j+BoVAb+a5G6YDPW3M5HOdMWQ==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
mimic-fn@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/mimic-fn/-/mimic-fn-2.1.0.tgz#7ed2c2ccccaf84d3ffcb7a69b57711fc2083401b"
integrity sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
minimalistic-assert@^1.0.0, minimalistic-assert@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/minimalistic-assert/-/minimalistic-assert-1.0.1.tgz#2e194de044626d4a10e7f7fbc00ce73e83e4d5c7"
integrity sha512-UtJcAD4yEaGtjPezWuO9wC4nwUnVH/8/Im3yEHQP4b67cXlD/Qr9hdITCU1xDbSEXg2XKNaP8jsReV7vQd00/A==
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
minimalistic-crypto-utils@^1.0.0, minimalistic-crypto-utils@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/minimalistic-crypto-utils/-/minimalistic-crypto-utils-1.0.1.tgz#f6c00c1c0b082246e5c4d99dfb8c7c083b2b582a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-9sAMHAsIIkblxNmd+4x8CDsrWCo=
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
minimatch@3.0.3:
version "3.0.3"
resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-3.0.3.tgz#2a4e4090b96b2db06a9d7df01055a62a77c9b774"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Kk5AkLlrLbBqnX3wEFWmKnfJt3Q=
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:
brace-expansion "^1.0.0"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
minimatch@^3.0.4:
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
version "3.0.4"
resolved "https://registry.yarnpkg.com/minimatch/-/minimatch-3.0.4.tgz#5166e286457f03306064be5497e8dbb0c3d32083"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-yJHVQEhyqPLUTgt9B83PXu6W3rx4MvvHvSUvToogpwoGDOUQ+yDrR0HRot+yOCdCO7u4hX3pWft6kWBBcqh0UA==
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:
brace-expansion "^1.1.7"
minimist@0.0.8:
version "0.0.8"
resolved "https://registry.yarnpkg.com/minimist/-/minimist-0.0.8.tgz#857fcabfc3397d2625b8228262e86aa7a011b05d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-hX/Kv8M5fSYluCKCYuhqp6ARsF0=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
minimist@^1.1.1, minimist@^1.2.0, "minimist@~ 1.2.0":
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
version "1.2.0"
resolved "https://registry.yarnpkg.com/minimist/-/minimist-1.2.0.tgz#a35008b20f41383eec1fb914f4cd5df79a264284"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-o1AIsg9BOD7sH7kU9M1d95omQoQ=
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
minimist@~0.0.1:
version "0.0.10"
resolved "https://registry.yarnpkg.com/minimist/-/minimist-0.0.10.tgz#de3f98543dbf96082be48ad1a0c7cda836301dcf"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-3j+YVD2/lggr5IrRoMfNqDYwHc8=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
minipass@^2.2.1, minipass@^2.3.5:
Update better-sqlite3 to v5 When we took a dep on better-sqlite3 in #836, we used a fork, because better-sqlite3 did not yet support private in-memory databases via the `:memory:` filepath. As of better-sqlite3 v5, this has been added to mainline, so we no longer need the fork. The v4->v5 transition involves some breaking changes. The only ones that affected us were two field renames, from `lastUpdateROWID` to `lastUpdateRowid`, and `returnsData` to `reader`. Test plan: After updating the field accesses, `yarn test --full` passes. For added safety, I also blew away cache, loaded a nontrivial repository, and verified that the full cred workflow still works. cc @wchargin
2019-07-04 16:48:34 +00:00
version "2.3.5"
resolved "https://registry.yarnpkg.com/minipass/-/minipass-2.3.5.tgz#cacebe492022497f656b0f0f51e2682a9ed2d848"
integrity sha512-Gi1W4k059gyRbyVUZQ4mEqLm0YIUiGYfvxhF6SIlk3ui1WVxMTGfGdQ2SInh3PDrRTVvPKgULkpJtT4RH10+VA==
dependencies:
safe-buffer "^5.1.2"
yallist "^3.0.0"
minizlib@^1.2.1:
version "1.2.1"
resolved "https://registry.yarnpkg.com/minizlib/-/minizlib-1.2.1.tgz#dd27ea6136243c7c880684e8672bb3a45fd9b614"
integrity sha512-7+4oTUOWKg7AuL3vloEWekXY2/D20cevzsrNT2kGWm+39J9hGTCBv8VI5Pm5lXZ/o3/mdR4f8rflAPhnQb8mPA==
dependencies:
minipass "^2.2.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
mississippi@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/mississippi/-/mississippi-3.0.0.tgz#ea0a3291f97e0b5e8776b363d5f0a12d94c67022"
integrity sha512-x471SsVjUtBRtcvd4BzKE9kFC+/2TeWgKCgw0bZcw1b9l2X3QX5vCWgF+KaZaYm87Ss//rHnWryupDrgLvmSkA==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
concat-stream "^1.5.0"
duplexify "^3.4.2"
end-of-stream "^1.1.0"
flush-write-stream "^1.0.0"
from2 "^2.1.0"
parallel-transform "^1.1.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
pump "^3.0.0"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
pumpify "^1.3.3"
stream-each "^1.1.0"
through2 "^2.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
mixin-deep@^1.2.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.3.2"
resolved "https://registry.yarnpkg.com/mixin-deep/-/mixin-deep-1.3.2.tgz#1120b43dc359a785dce65b55b82e257ccf479566"
integrity sha512-WRoDn//mXBiJ1H40rqa3vH0toePwSsGb45iInWlTySa+Uu4k3tYUSxa2v1KqAiLtvlrSzaExqS1gtk96A9zvEA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
for-in "^1.0.2"
is-extendable "^1.0.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
mkdirp@0.5.x, mkdirp@^0.5.0, mkdirp@^0.5.1, mkdirp@~0.5.0:
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
version "0.5.1"
resolved "https://registry.yarnpkg.com/mkdirp/-/mkdirp-0.5.1.tgz#30057438eac6cf7f8c4767f38648d6697d75c903"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-MAV0OOrGz3+MR2fzhkjWaX11yQM=
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:
minimist "0.0.8"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
moo@^0.4.3:
version "0.4.3"
resolved "https://registry.yarnpkg.com/moo/-/moo-0.4.3.tgz#3f847a26f31cf625a956a87f2b10fbc013bfd10e"
integrity sha512-gFD2xGCl8YFgGHsqJ9NKRVdwlioeW3mI1iqfLNYQOv0+6JRwG58Zk9DIGQgyIaffSYaO1xsKnMaYzzNr1KyIAw==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
move-concurrently@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/move-concurrently/-/move-concurrently-1.0.1.tgz#be2c005fda32e0b29af1f05d7c4b33214c701f92"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-viwAX9oy4LKa8fBdfEszIUxwH5I=
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
aproba "^1.1.1"
copy-concurrently "^1.0.0"
fs-write-stream-atomic "^1.0.8"
mkdirp "^0.5.1"
rimraf "^2.5.4"
run-queue "^1.0.3"
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
ms@2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/ms/-/ms-2.0.0.tgz#5608aeadfc00be6c2901df5f9861788de0d597c8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-VgiurfwAvmwpAd9fmGF4jeDVl8g=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
ms@2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/ms/-/ms-2.1.1.tgz#30a5864eb3ebb0a66f2ebe6d727af06a09d86e0a"
integrity sha512-tgp+dl5cGk28utYktBsrFqA7HKgrhgPsg6Z/EfhWI4gl1Hwq8B/GmY/0oXZ6nF8hDVesS/FpnYaD/kOWhYQvyg==
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
ms@^2.1.1:
version "2.1.2"
resolved "https://registry.yarnpkg.com/ms/-/ms-2.1.2.tgz#d09d1f357b443f493382a8eb3ccd183872ae6009"
integrity sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==
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
multicast-dns-service-types@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/multicast-dns-service-types/-/multicast-dns-service-types-1.1.0.tgz#899f11d9686e5e05cb91b35d5f0e63b773cfc901"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-iZ8R2WhuXgXLkbNdXw5jt3PPyQE=
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
multicast-dns@^6.0.1:
version "6.2.3"
resolved "https://registry.yarnpkg.com/multicast-dns/-/multicast-dns-6.2.3.tgz#a0ec7bd9055c4282f790c3c82f4e28db3b31b229"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-ji6J5enbMyGRHIAkAOu3WdV8nggqviKCEKtXcOqfphZZtQrmHKycfynJ2V7eVPUA4NhJ6V7Wf4TmGbTwKE9B6g==
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:
dns-packet "^1.3.1"
thunky "^1.0.2"
mute-stream@0.0.7:
version "0.0.7"
resolved "https://registry.yarnpkg.com/mute-stream/-/mute-stream-0.0.7.tgz#3075ce93bc21b8fab43e1bc4da7e8115ed1e7bab"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-MHXOk7whuPq0PhvE2n6BFe0ee6s=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
nan@^2.12.1:
version "2.14.0"
resolved "https://registry.yarnpkg.com/nan/-/nan-2.14.0.tgz#7818f722027b2459a86f0295d434d1fc2336c52c"
integrity sha512-INOFj37C7k3AfaNTtX8RhsTw7qRy7eLET14cROi9+5HAVbbHuIWUHEauBv5qT4Av2tWasiTY1Jw6puUNqRJXQg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
nanomatch@^1.2.9:
version "1.2.13"
resolved "https://registry.yarnpkg.com/nanomatch/-/nanomatch-1.2.13.tgz#b87a8aa4fc0de8fe6be88895b38983ff265bd119"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-fpoe2T0RbHwBTBUOftAfBPaDEi06ufaUai0mE6Yn1kacc3SnTErfb/h+X94VXzI64rKFHYImXSvdwGGCmwOqCA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
arr-diff "^4.0.0"
array-unique "^0.3.2"
define-property "^2.0.2"
extend-shallow "^3.0.2"
fragment-cache "^0.2.1"
is-windows "^1.0.2"
kind-of "^6.0.2"
object.pick "^1.3.0"
regex-not "^1.0.0"
snapdragon "^0.8.1"
to-regex "^3.0.1"
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
natural-compare@^1.4.0:
version "1.4.0"
resolved "https://registry.yarnpkg.com/natural-compare/-/natural-compare-1.4.0.tgz#4abebfeed7541f2c27acfb29bdbbd15c8d5ba4f7"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Sr6/7tdUHywnrPspvbvRXI1bpPc=
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
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
nearley@^2.7.10:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.16.0"
resolved "https://registry.yarnpkg.com/nearley/-/nearley-2.16.0.tgz#77c297d041941d268290ec84b739d0ee297e83a7"
integrity sha512-Tr9XD3Vt/EujXbZBv6UAHYoLUSMQAxSsTnm9K3koXzjzNWY195NqALeyrzLZBKzAkL3gl92BcSogqrHjD8QuUg==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
commander "^2.19.0"
moo "^0.4.3"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
railroad-diagrams "^1.0.0"
randexp "0.4.6"
semver "^5.4.1"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
needle@^2.2.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.4.0"
resolved "https://registry.yarnpkg.com/needle/-/needle-2.4.0.tgz#6833e74975c444642590e15a750288c5f939b57c"
integrity sha512-4Hnwzr3mi5L97hMYeNl8wRW/Onhy4nUKR/lVemJ8gJedxxUyBLm9kkrDColJvoSfwi0jCNhD+xCdOtiGDQiRZg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
debug "^3.2.6"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
iconv-lite "^0.4.4"
sax "^1.2.4"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
negotiator@0.6.2:
version "0.6.2"
resolved "https://registry.yarnpkg.com/negotiator/-/negotiator-0.6.2.tgz#feacf7ccf525a77ae9634436a64883ffeca346fb"
integrity sha512-hZXc7K2e+PgeI1eDBe/10Ard4ekbfrrqG8Ep+8Jmf4JID2bNg7NvCPOZN+kfF574pFQI7mum2AUqDidoKqcTOw==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
neo-async@^2.5.0, neo-async@^2.6.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "2.6.1"
resolved "https://registry.yarnpkg.com/neo-async/-/neo-async-2.6.1.tgz#ac27ada66167fa8849a6addd837f6b189ad2081c"
integrity sha512-iyam8fBuCUpWeKPGpaNMetEocMt364qkCsfL9JuhjXX6dRnguRVOfk2GZaDpPjcOKiiXCPINZC1GczQ7iTq3Zw==
nice-try@^1.0.4:
version "1.0.5"
resolved "https://registry.yarnpkg.com/nice-try/-/nice-try-1.0.5.tgz#a3378a7696ce7d223e88fc9b764bd7ef1089e366"
integrity sha512-1nh45deeb5olNY7eX82BkPO7SSxR5SSYJiPTrTdFUVYwAl8CKMA5N9PjTYkHiRjisVcxcQ1HXdLhx2qxxJzLNQ==
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
node-fetch@2.1.2:
version "2.1.2"
resolved "https://registry.yarnpkg.com/node-fetch/-/node-fetch-2.1.2.tgz#ab884e8e7e57e38a944753cec706f788d1768bb5"
integrity sha1-q4hOjn5X44qUR1POxwb3iNF2i7U=
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
node-fetch@^1.0.1:
version "1.7.3"
resolved "https://registry.yarnpkg.com/node-fetch/-/node-fetch-1.7.3.tgz#980f6f72d85211a5347c6b2bc18c5b84c3eb47ef"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-NhZ4CsKx7cYm2vSrBAr2PvFOe6sWDf0UYLRqA6svUYg7+/TSfVAu49jYC4BvQ4Sms9SZgdqGBgroqfDhJdTyKQ==
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:
encoding "^0.1.11"
is-stream "^1.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
node-forge@0.7.5:
version "0.7.5"
resolved "https://registry.yarnpkg.com/node-forge/-/node-forge-0.7.5.tgz#6c152c345ce11c52f465c2abd957e8639cd674df"
integrity sha512-MmbQJ2MTESTjt3Gi/3yG1wGpIMhUfcIypUCGtTizFR9IiccFwxSpfp0vtIZlkFclEqERemxfnSdZEMR9VqqEFQ==
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
node-int64@^0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/node-int64/-/node-int64-0.4.0.tgz#87a9065cdb355d3182d8f94ce11188b825c68a3b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-h6kGXNs1XTGC2PlM4RGIuCXGijs=
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
node-libs-browser@^2.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.2.1"
resolved "https://registry.yarnpkg.com/node-libs-browser/-/node-libs-browser-2.2.1.tgz#b64f513d18338625f90346d27b0d235e631f6425"
integrity sha512-h/zcD8H9kaDZ9ALUWwlBUDo6TKF8a7qBSCSEGfjTVIYeqsioSKaAX+BN7NgiMGp6iSIXZ3PxgCu8KS3b71YK5Q==
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:
assert "^1.1.1"
browserify-zlib "^0.2.0"
buffer "^4.3.0"
console-browserify "^1.1.0"
constants-browserify "^1.0.0"
crypto-browserify "^3.11.0"
domain-browser "^1.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
events "^3.0.0"
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
https-browserify "^1.0.0"
os-browserify "^0.3.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
path-browserify "0.0.1"
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
process "^0.11.10"
punycode "^1.2.4"
querystring-es3 "^0.2.0"
readable-stream "^2.3.3"
stream-browserify "^2.0.1"
stream-http "^2.7.2"
string_decoder "^1.0.0"
timers-browserify "^2.0.4"
tty-browserify "0.0.0"
url "^0.11.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
util "^0.11.0"
vm-browserify "^1.0.1"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
node-modules-regexp@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/node-modules-regexp/-/node-modules-regexp-1.0.0.tgz#8d9dbe28964a4ac5712e9131642107c71e90ec40"
integrity sha1-jZ2+KJZKSsVxLpExZCEHxx6Q7EA=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
node-notifier@^5.2.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "5.4.0"
resolved "https://registry.yarnpkg.com/node-notifier/-/node-notifier-5.4.0.tgz#7b455fdce9f7de0c63538297354f3db468426e6a"
integrity sha512-SUDEb+o71XR5lXSTyivXd9J7fCloE3SyP4lSgt3lU2oSANiox+SxlNRGPjDKrwU1YN3ix2KN/VGGCg0t01rttQ==
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:
growly "^1.3.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
is-wsl "^1.1.0"
semver "^5.5.0"
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
shellwords "^0.1.1"
which "^1.3.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
node-pre-gyp@^0.12.0:
version "0.12.0"
resolved "https://registry.yarnpkg.com/node-pre-gyp/-/node-pre-gyp-0.12.0.tgz#39ba4bb1439da030295f899e3b520b7785766149"
integrity sha512-4KghwV8vH5k+g2ylT+sLTjy5wmUOb9vPhnM8NHvRf9dHmnW/CndrFXy2aRPaPST6dugXSdHXfeaHQm77PIz/1A==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
detect-libc "^1.0.2"
mkdirp "^0.5.1"
needle "^2.2.1"
nopt "^4.0.1"
npm-packlist "^1.1.6"
npmlog "^4.0.2"
rc "^1.2.7"
rimraf "^2.6.1"
semver "^5.3.0"
tar "^4"
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
node-releases@^1.1.25:
version "1.1.25"
resolved "https://registry.yarnpkg.com/node-releases/-/node-releases-1.1.25.tgz#0c2d7dbc7fed30fbe02a9ee3007b8c90bf0133d3"
integrity sha512-fI5BXuk83lKEoZDdH3gRhtsNgh05/wZacuXkgbiYkceE7+QIMXOg98n9ZV7mz27B+kFHnqHcUpscZZlGRSmTpQ==
dependencies:
semver "^5.3.0"
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
nopt@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/nopt/-/nopt-4.0.1.tgz#d0d4685afd5415193c8c7505602d0d17cd64474d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-0NRoWv1UFRk8jHUFYC0NF81kR00=
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:
abbrev "1"
osenv "^0.1.4"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
normalize-package-data@^2.3.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.5.0"
resolved "https://registry.yarnpkg.com/normalize-package-data/-/normalize-package-data-2.5.0.tgz#e66db1838b200c1dfc233225d12cb36520e234a8"
integrity sha512-/5CMN3T0R4XTj4DcGaexo+roZSdSFW/0AOOTROrjxzCG1wrWXEsGbRKevjlIL+ZDE4sZlJr5ED4YW0yqmkK+eA==
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:
hosted-git-info "^2.1.4"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
resolve "^1.10.0"
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
semver "2 || 3 || 4 || 5"
validate-npm-package-license "^3.0.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
normalize-path@^2.1.1:
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
version "2.1.1"
resolved "https://registry.yarnpkg.com/normalize-path/-/normalize-path-2.1.1.tgz#1ab28b556e198363a8c1a6f7e6fa20137fe6aed9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-GrKLVW4Zg2Oowab35vogE3/mrtk=
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:
remove-trailing-separator "^1.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
normalize-path@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/normalize-path/-/normalize-path-3.0.0.tgz#0dcd69ff23a1c9b11fd0978316644a0388216a65"
integrity sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
npm-bundled@^1.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.6"
resolved "https://registry.yarnpkg.com/npm-bundled/-/npm-bundled-1.0.6.tgz#e7ba9aadcef962bb61248f91721cd932b3fe6bdd"
integrity sha512-8/JCaftHwbd//k6y2rEWp6k1wxVfpFzB6t1p825+cUb7Ym2XQfhwIC5KwhrvzZRJu+LtDE585zVaS32+CGtf0g==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
npm-packlist@^1.1.6:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.4.4"
resolved "https://registry.yarnpkg.com/npm-packlist/-/npm-packlist-1.4.4.tgz#866224233850ac534b63d1a6e76050092b5d2f44"
integrity sha512-zTLo8UcVYtDU3gdeaFu2Xu0n0EvelfHDGuqtNIn5RO7yQj4H1TqNdBc/yZjxnWA0PVB8D3Woyp0i5B43JwQ6Vw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
ignore-walk "^3.0.1"
npm-bundled "^1.0.1"
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
npm-run-path@^2.0.0:
version "2.0.2"
resolved "https://registry.yarnpkg.com/npm-run-path/-/npm-run-path-2.0.2.tgz#35a9232dfa35d7067b4cb2ddf2357b1871536c5f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-NakjLfo11wZ7TLLd8jV7GHFTbF8=
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:
path-key "^2.0.0"
npmlog@^4.0.2:
version "4.1.2"
resolved "https://registry.yarnpkg.com/npmlog/-/npmlog-4.1.2.tgz#08a7f2a8bf734604779a9efa4ad5cc717abb954b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-2uUqazuKlTaSI/dC8AzicUck7+IrEaOnN/e0jd3Xtt1KcGpwx30v50mL7oPyr/h9bL3E4aZccVwpwP+5W9Vjkg==
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:
are-we-there-yet "~1.1.2"
console-control-strings "~1.1.0"
gauge "~2.7.3"
set-blocking "~2.0.0"
nth-check@~1.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/nth-check/-/nth-check-1.0.2.tgz#b2bd295c37e3dd58a3bf0700376663ba4d9cf05c"
integrity sha512-WeBOdju8SnzPN5vTUJYxYUxLeXpCaVP5i5e0LF8fg7WORF2Wd7wFX/pk0tYZk7s8T+J7VLy0Da6J1+wCT0AtHg==
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:
boolbase "~1.0.0"
number-is-nan@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/number-is-nan/-/number-is-nan-1.0.1.tgz#097b602b53422a522c1afb8790318336941a011d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-CXtgK1NCKlIsGvuHkDGDNpQaAR0=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
nwsapi@^2.0.7:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.1.4"
resolved "https://registry.yarnpkg.com/nwsapi/-/nwsapi-2.1.4.tgz#e006a878db23636f8e8a67d33ca0e4edf61a842f"
integrity sha512-iGfd9Y6SFdTNldEy2L0GUhcarIutFmk+MPWIn9dmj8NMIup03G08uUF2KGbbmv/Ux4RT0VZJoP/sVbWA6d/VIw==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
oauth-sign@~0.9.0:
version "0.9.0"
resolved "https://registry.yarnpkg.com/oauth-sign/-/oauth-sign-0.9.0.tgz#47a7b016baa68b5fa0ecf3dee08a85c679ac6455"
integrity sha512-fexhUFFPTGV8ybAtSIGbV6gOkSv8UtRbDBnAyLQw4QPKkgNlsH2ByPGtMUqdWkos6YCRmAqViwgZrJc/mRDzZQ==
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
object-assign@4.1.1, object-assign@^4.0.1, object-assign@^4.1.0, object-assign@^4.1.1:
version "4.1.1"
resolved "https://registry.yarnpkg.com/object-assign/-/object-assign-4.1.1.tgz#2109adc7965887cfc05cbbd442cac8bfbb360863"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-IQmtx5ZYh8/AXLvUQsrIv7s2CGM=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
object-copy@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/object-copy/-/object-copy-0.1.0.tgz#7e7d858b781bd7c991a41ba975ed3812754e998c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-fn2Fi3gb18mRpBupde04EnVOmYw=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
copy-descriptor "^0.1.0"
define-property "^0.2.5"
kind-of "^3.0.3"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
object-inspect@^1.6.0:
version "1.6.0"
resolved "https://registry.yarnpkg.com/object-inspect/-/object-inspect-1.6.0.tgz#c70b6cbf72f274aab4c34c0c82f5167bf82cf15b"
integrity sha512-GJzfBZ6DgDAmnuaM3104jR4s1Myxr3Y3zfIyN4z3UdqN69oSRacNK8UhnobDdC+7J2AHCjGwxQubNJfE70SXXQ==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
object-is@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/object-is/-/object-is-1.0.1.tgz#0aa60ec9989a0b3ed795cf4d06f62cf1ad6539b6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-CqYOyZiaCz7Xlc9NBvYs8a1lObY=
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
object-keys@^1.0.11, object-keys@^1.0.12:
version "1.1.1"
resolved "https://registry.yarnpkg.com/object-keys/-/object-keys-1.1.1.tgz#1c47f272df277f3b1daf061677d9c82e2322c60e"
integrity sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
object-visit@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/object-visit/-/object-visit-1.0.1.tgz#f79c4493af0c5377b59fe39d395e41042dd045bb"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-95xEk68MU3e1n+OdOV5BBC3QRbs=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
isobject "^3.0.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
object.assign@^4.1.0:
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
version "4.1.0"
resolved "https://registry.yarnpkg.com/object.assign/-/object.assign-4.1.0.tgz#968bf1100d7956bb3ca086f006f846b3bc4008da"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-exHJeq6kBKj58mqGyTQ9DFvrZC/eR6OwxzoM9YRoGBqrXYonaFyGiFMuc9VZrXf7DarreEwMpurG3dd+CNyW5w==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
define-properties "^1.1.2"
function-bind "^1.1.1"
has-symbols "^1.0.0"
object-keys "^1.0.11"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
object.entries@^1.0.4, object.entries@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/object.entries/-/object.entries-1.1.0.tgz#2024fc6d6ba246aee38bdb0ffd5cfbcf371b7519"
integrity sha512-l+H6EQ8qzGRxbkHOd5I/aHRhHDKoQXQ8g0BYt4uSweQU1/J6dZUOyWh9a2Vky35YCKjzmgxOzta2hH6kf9HuXA==
dependencies:
define-properties "^1.1.3"
es-abstract "^1.12.0"
function-bind "^1.1.1"
has "^1.0.3"
object.fromentries@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/object.fromentries/-/object.fromentries-2.0.0.tgz#49a543d92151f8277b3ac9600f1e930b189d30ab"
integrity sha512-9iLiI6H083uiqUuvzyY6qrlmc/Gz8hLQFOcb/Ri/0xXFkSNS3ctV+CbE6yM2+AnkYfOB3dGjdzC0wrMLIhQICA==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
define-properties "^1.1.2"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
es-abstract "^1.11.0"
function-bind "^1.1.1"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
has "^1.0.1"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
object.getownpropertydescriptors@^2.0.3:
version "2.0.3"
resolved "https://registry.yarnpkg.com/object.getownpropertydescriptors/-/object.getownpropertydescriptors-2.0.3.tgz#8758c846f5b407adab0f236e0986f14b051caa16"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-h1jIRvW0B62rDyNuCYbxSwUcqhY=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
define-properties "^1.1.2"
es-abstract "^1.5.1"
object.pick@^1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/object.pick/-/object.pick-1.3.0.tgz#87a10ac4c1694bd2e1cbf53591a66141fb5dd747"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-h6EKxMFpS9Lhy/U1kaZhQftd10c=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
isobject "^3.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
object.values@^1.0.4, object.values@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/object.values/-/object.values-1.1.0.tgz#bf6810ef5da3e5325790eaaa2be213ea84624da9"
integrity sha512-8mf0nKLAoFX6VlNVdhGj31SVYpaNFtUnuoOXWyFEstsWRgU837AK+JYM0iAxwkSzGRbwn8cbFmgbyxj1j4VbXg==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
define-properties "^1.1.3"
es-abstract "^1.12.0"
function-bind "^1.1.1"
has "^1.0.3"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
obuf@^1.0.0, obuf@^1.1.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.2"
resolved "https://registry.yarnpkg.com/obuf/-/obuf-1.1.2.tgz#09bea3343d41859ebd446292d11c9d4db619084e"
integrity sha512-PX1wu0AmAdPqOL1mWhqmlOd8kOIZQwGZw6rh7uby9fTc5lhaOWFLX3I6R1hrF9k3zUY40e6igsLGkDXK92LJNg==
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
on-finished@~2.3.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/on-finished/-/on-finished-2.3.0.tgz#20f1336481b083cd75337992a16971aa2d906947"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-IPEzZIGwg811M3mSoWlxqi2QaUc=
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:
ee-first "1.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
on-headers@~1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/on-headers/-/on-headers-1.0.2.tgz#772b0ae6aaa525c399e489adfad90c403eb3c28f"
integrity sha512-pZAE+FJLoyITytdqK0U5s+FIpjN0JP3OzFi/u8Rx+EV5/W+JTWGXG8xFzevE7AjBfDqHv/8vL8qQsIhHnqRkrA==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
once@^1.3.0, once@^1.3.1, once@^1.4.0:
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
version "1.4.0"
resolved "https://registry.yarnpkg.com/once/-/once-1.4.0.tgz#583b1aa775961d4b113ac17d9c50baef9dd76bd1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-WDsap3WWHUsROsF9nFC6753Xa9E=
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:
wrappy "1"
onetime@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/onetime/-/onetime-2.0.1.tgz#067428230fd67443b2794b22bba528b6867962d4"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-BnQoIw/WdEOyeUsiu6UotoZ5YtQ=
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:
mimic-fn "^1.0.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
opn@5.2.0:
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
version "5.2.0"
resolved "https://registry.yarnpkg.com/opn/-/opn-5.2.0.tgz#71fdf934d6827d676cecbea1531f95d354641225"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-Jd/GpzPyHF4P2/aNOVmS3lfMSWV9J7cOhCG1s08XCEAsPkB7lp6ddiU0J7XzyQRDUh8BqJ7PchfINjR8jyofRQ==
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:
is-wsl "^1.1.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
opn@^5.5.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "5.5.0"
resolved "https://registry.yarnpkg.com/opn/-/opn-5.5.0.tgz#fc7164fab56d235904c51c3b27da6758ca3b9bfc"
integrity sha512-PqHpggC9bLV0VeWcdKhkpxY+3JTzetLSqTCWL/z/tFIbI6G8JCjondXklT1JinczLz2Xib62sSp0T/gKT4KksA==
dependencies:
is-wsl "^1.1.0"
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
optimist@^0.6.1:
version "0.6.1"
resolved "https://registry.yarnpkg.com/optimist/-/optimist-0.6.1.tgz#da3ea74686fa21a19a111c326e90eb15a0196686"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-2j6nRob6IaGaERwybpDrFaAZZoY=
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:
minimist "~0.0.1"
wordwrap "~0.0.2"
optionator@^0.8.1, optionator@^0.8.2:
version "0.8.2"
resolved "https://registry.yarnpkg.com/optionator/-/optionator-0.8.2.tgz#364c5e409d3f4d6301d6c0b4c05bba50180aeb64"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-NkxeQJ0/TWMB1sC0wFu6UBgK62Q=
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:
deep-is "~0.1.3"
fast-levenshtein "~2.0.4"
levn "~0.3.0"
prelude-ls "~1.1.2"
type-check "~0.3.2"
wordwrap "~1.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
original@>=0.0.5, original@^1.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/original/-/original-1.0.2.tgz#e442a61cffe1c5fd20a65f3261c26663b303f25f"
integrity sha512-hyBVl6iqqUOJ8FqRe+l/gS8H+kKYjrEndd5Pm1MfBtsEKA038HkkdbAl/72EAXGyonD/PFsvmVG+EvcIpliMBg==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
url-parse "^1.4.3"
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
os-browserify@^0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/os-browserify/-/os-browserify-0.3.0.tgz#854373c7f5c2315914fc9bfc6bd8238fdda1ec27"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-hUNzx/XCMVkU/Jv8a9gjj92h7Cc=
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
deps: remove some unused packages (#789) Summary: Mostly Webpack loaders that have become unused through various config changes. Test Plan: Check that these packages are not used anywhere except as transitive dependencies: ```shell $ git show --format= package.json | > sed '1,4d' | grep '^-' | cut -d\" -f2 | git grep -cf - yarn.lock:3 ``` Also, `yarn && yarn test --full` works, and `yarn start` works, and `yarn backend && node ./bin/sourcecred.js load sourcecred/example-git` works. wchargin-branch: remove-unused-deps
2018-09-06 19:08:45 +00:00
os-homedir@^1.0.0:
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
version "1.0.2"
resolved "https://registry.yarnpkg.com/os-homedir/-/os-homedir-1.0.2.tgz#ffbc4988336e0e833de0c168c7ef152121aa7fb3"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-/7xJiDNuDoM94MFox+8VISGqf7M=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
os-locale@^3.0.0, os-locale@^3.1.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "3.1.0"
resolved "https://registry.yarnpkg.com/os-locale/-/os-locale-3.1.0.tgz#a802a6ee17f24c10483ab9935719cef4ed16bf1a"
integrity sha512-Z8l3R4wYWM40/52Z+S265okfFj8Kt2cC2MKY+xNi3kFs+XGI7WXu/I309QQQYbRW4ijiZ+yxs9pqEhJh0DqW3Q==
dependencies:
execa "^1.0.0"
lcid "^2.0.0"
mem "^4.0.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
os-tmpdir@^1.0.0, os-tmpdir@~1.0.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
version "1.0.2"
resolved "https://registry.yarnpkg.com/os-tmpdir/-/os-tmpdir-1.0.2.tgz#bbe67406c79aa85c5cfec766fe5734555dfa1274"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-u+Z0BseaqFxc/sdm/lc0VV36EnQ=
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
osenv@^0.1.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "0.1.5"
resolved "https://registry.yarnpkg.com/osenv/-/osenv-0.1.5.tgz#85cdfafaeb28e8677f416e287592b5f3f49ea410"
integrity sha512-0CWcCECdMVc2Rw3U5w9ZjqX6ga6ubk1xDVKxtBQPK7wis/0F2r9T6k4ydGYhecl7YUBxBVxhL5oisPsNxAPe2g==
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:
os-homedir "^1.0.0"
os-tmpdir "^1.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
p-defer@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/p-defer/-/p-defer-1.0.0.tgz#9f6eb182f6c9aa8cd743004a7d4f96b196b0fb0c"
integrity sha1-n26xgvbJqozXQwBKfU+WsZaw+ww=
p-each-series@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/p-each-series/-/p-each-series-1.0.0.tgz#930f3d12dd1f50e7434457a22cd6f04ac6ad7f71"
integrity sha1-kw89Et0fUOdDRFeiLNbwSsatf3E=
dependencies:
p-reduce "^1.0.0"
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
p-finally@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/p-finally/-/p-finally-1.0.0.tgz#3fbcfb15b899a44123b34b6dcc18b724336a2cae"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-P7z7FbiZpEEjs0ttzBi3JDNqLK4=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
p-is-promise@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/p-is-promise/-/p-is-promise-2.1.0.tgz#918cebaea248a62cf7ffab8e3bca8c5f882fc42e"
integrity sha512-Y3W0wlRPK8ZMRbNq97l4M5otioeA5lm1z7bkNkxCka8HSPjR0xRWmpCmc9utiaLP9Jb1eD8BgeIxTW4AIF45Pg==
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
p-limit@^1.1.0:
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/p-limit/-/p-limit-1.3.0.tgz#b86bd5f0c25690911c7590fcbfc2010d54b3ccb8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-vvcXsLAJ9Dr5rQOPk7toZQZJApBl2K4J6dANSsEuh6QI41JYcsS/qhTGa9ErIUUgK3WNQoJYvylxvjqmiqEA9Q==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
p-try "^1.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
p-limit@^2.0.0, p-limit@^2.2.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "2.2.0"
resolved "https://registry.yarnpkg.com/p-limit/-/p-limit-2.2.0.tgz#417c9941e6027a9abcba5092dd2904e255b5fbc2"
integrity sha512-pZbTJpoUsCzV48Mc9Nh51VbwO0X9cuPFE8gYwx9BTCt9SF8/b7Zljd2fVgOxhIF/HDTKgpVzs+GPhyKfjLLFRQ==
dependencies:
p-try "^2.0.0"
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
p-locate@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-2.0.0.tgz#20a0103b222a70c8fd39cc2e580680f3dde5ec43"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-IKAQOyIqcMj9OcwuWAaA893l7EM=
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:
p-limit "^1.1.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
p-locate@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/p-locate/-/p-locate-3.0.0.tgz#322d69a05c0264b25997d9f40cd8a891ab0064a4"
integrity sha512-x+12w/To+4GFfgJhBEpiDcLozRJGegY+Ei7/z0tSLkMmxGZNybVMSfWj9aJn8Z5Fc7dBUNJOOVgPv2H7IwulSQ==
dependencies:
p-limit "^2.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
p-map@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/p-map/-/p-map-2.1.0.tgz#310928feef9c9ecc65b68b17693018a665cea175"
integrity sha512-y3b8Kpd8OAN444hxfBbFfj1FY/RjtTd8tzYwhUqNYXx0fXx2iX4maP4Qr6qhIKbQXI02wTLAda4fYUbDagTUFw==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
p-reduce@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/p-reduce/-/p-reduce-1.0.0.tgz#18c2b0dd936a4690a529f8231f58a0fdb6a47dfa"
integrity sha1-GMKw3ZNqRpClKfgjH1ig/bakffo=
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
p-retry@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/p-retry/-/p-retry-3.0.1.tgz#316b4c8893e2c8dc1cfa891f406c4b422bebf328"
integrity sha512-XE6G4+YTTkT2a0UWb2kjZe8xNwf8bIbnqpc/IS/idOBVhyves0mK5OJgeocjx7q5pvX/6m23xuzVPYT1uGM73w==
dependencies:
retry "^0.12.0"
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
p-try@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/p-try/-/p-try-1.0.0.tgz#cbc79cdbaf8fd4228e13f621f2b1a237c1b207b3"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-y8ec26+P1CKOE/Yh8rGiN8GyB7M=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
p-try@^2.0.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/p-try/-/p-try-2.2.0.tgz#cb2868540e313d61de58fafbe35ce9004d5540e6"
integrity sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==
Store GitHub data gzipped at rest (#751) Summary: We store the relational view in `view.json.gz` instead of `view.json`, taking advantage of the isomorphic `pako` library for gzip encoding and decoding. Sample space savings (note that post bodies are included; i.e., #747 has not been applied): SAVE OLD (B) NEW (B) REPO 89.7% 25326 2617 sourcecred/example-github 82.9% 3257576 555948 sourcecred/sourcecred 85.2% 11287621 1665884 ipfs/js-ipfs 88.0% 20953425 2520358 gitcoinco/web 84.4% 38196825 5951459 ipfs/go-ipfs 84.9% 205770642 31101452 tensorflow/tensorflow <details> <summary>Script to generate space savings output</summary> ```shell savings() { printf '% 7s % 11s % 11s %s\n' 'SAVE' 'OLD (B)' 'NEW (B)' 'REPO' for repo; do file="${SOURCECRED_DIRECTORY}/data/${repo}/github/view.json.gz" if ! [ -f "${file}" ]; then printf >&2 'warn: no such file %s\n' "${file}" continue fi script="$(sed -e 's/^ *//' <<EOF repo = '${repo}' pre_size = $(<"${file}" gzip -dc | wc -c) post_size = $(<"${file}" wc -c) percentage = '%0.1f%%' % (100 * (1 - post_size / pre_size)) p = '% 7s % 11d % 11d %s' % (percentage, pre_size, post_size, repo) print(p) EOF )" python3 -c "${script}" done } ``` </details> Closes #750. Test Plan: Comparing the raw old version with the decompressed new version shows that they are identical: ``` $ <~/tmp/sourcecred/data/sourcecred/example-github/github/view.json \ > shasum -a 256 - 63853b9d3f918274aafacf5198787e18185a61b9c95faf640a1e61f5d11fa19f - $ <~/tmp/sourcecred/data/sourcecred/example-github/github/view.json.gz \ > gzip -dc | shasum -a 256 63853b9d3f918274aafacf5198787e18185a61b9c95faf640a1e61f5d11fa19f - ``` Additionally, `yarn test --full` passes, and `yarn start` still loads data and runs PageRank properly. wchargin-branch: gzip-relational-view
2018-09-01 17:42:30 +00:00
pako@^1.0.6, pako@~1.0.5:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.10"
resolved "https://registry.yarnpkg.com/pako/-/pako-1.0.10.tgz#4328badb5086a426aa90f541977d4955da5c9732"
integrity sha512-0DTvPVU3ed8+HNXOu5Bs+o//Mbdj9VNQMUOe9oKCwh8l0GNwpTDMKCWbRjgtD291AWnkAgkqA/LOnQS8AmS1tw==
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
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
parallel-transform@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/parallel-transform/-/parallel-transform-1.1.0.tgz#d410f065b05da23081fcd10f28854c29bda33b06"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-1BDwZbBdojCB/NEPKIVMKb2jOwY=
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
cyclist "~0.2.2"
inherits "^2.0.3"
readable-stream "^2.1.5"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
parent-module@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/parent-module/-/parent-module-1.0.1.tgz#691d2709e78c79fae3a156622452d00762caaaa2"
integrity sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==
dependencies:
callsites "^3.0.0"
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
parse-asn1@^5.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "5.1.4"
resolved "https://registry.yarnpkg.com/parse-asn1/-/parse-asn1-5.1.4.tgz#37f6628f823fbdeb2273b4d540434a22f3ef1fcc"
integrity sha512-Qs5duJcuvNExRfFZ99HDD3z4mAi3r9Wl/FOjEOijlxwCZs7E7mW2vjTpgQ4J8LpTF8x5v+1Vn5UQFejmWT11aw==
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:
asn1.js "^4.0.0"
browserify-aes "^1.0.0"
create-hash "^1.1.0"
evp_bytestokey "^1.0.0"
pbkdf2 "^3.0.3"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
safe-buffer "^5.1.1"
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
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
parse-entities@^1.1.0:
version "1.2.2"
resolved "https://registry.yarnpkg.com/parse-entities/-/parse-entities-1.2.2.tgz#c31bf0f653b6661354f8973559cb86dd1d5edf50"
integrity sha512-NzfpbxW/NPrzZ/yYSoQxyqUZMZXIdCfE0OIN4ESsnptHJECoUk3FZktxNuzQf4tjt5UEopnxpYJbvYuxIFDdsg==
dependencies:
character-entities "^1.0.0"
character-entities-legacy "^1.0.0"
character-reference-invalid "^1.0.0"
is-alphanumerical "^1.0.0"
is-decimal "^1.0.0"
is-hexadecimal "^1.0.0"
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
parse-json@^2.2.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/parse-json/-/parse-json-2.2.0.tgz#f480f40434ef80741f8469099f8dea18f55a4dc9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-9ID0BDTvgHQfhGkJn43qGPVaTck=
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:
error-ex "^1.2.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
parse-json@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/parse-json/-/parse-json-4.0.0.tgz#be35f5425be1f7f6c747184f98a788cb99477ee0"
integrity sha1-vjX1Qlvh9/bHRxhPmKeIy5lHfuA=
dependencies:
error-ex "^1.3.1"
json-parse-better-errors "^1.0.1"
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
parse-passwd@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/parse-passwd/-/parse-passwd-1.0.0.tgz#6d5b934a456993b23d37f40a382d6f1666a8e5c6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-bVuTSkVpk7I9N/QKOC1vFmao5cY=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
parse5@4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/parse5/-/parse5-4.0.0.tgz#6d78656e3da8d78b4ec0b906f7c08ef1dfe3f608"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-VrZ7eOd3T1Fk4XWNXMgiGBK/z0MG48BWG2uQNU4I72fkQuKUTZpl+u9k+CxEG0twMVzSmXEEz12z5Fnw1jIQFA==
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
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
parse5@^3.0.1:
version "3.0.3"
resolved "https://registry.yarnpkg.com/parse5/-/parse5-3.0.3.tgz#042f792ffdd36851551cf4e9e066b3874ab45b5c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-rgO9Zg5LLLkfJF9E6CCmXlSE4UVceloys8JrFqCcHloC3usd/kJCyPDwH2SOlzix2j3xaP9sUX3e8+kvkuleAA==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
"@types/node" "*"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
parseurl@~1.3.2, parseurl@~1.3.3:
version "1.3.3"
resolved "https://registry.yarnpkg.com/parseurl/-/parseurl-1.3.3.tgz#9da19e7bee8d12dff0513ed5b76957793bc2e8d4"
integrity sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ==
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
pascalcase@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/pascalcase/-/pascalcase-0.1.1.tgz#b363e55e8006ca6fe21784d2db22bd15d7917f14"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-s2PlXoAGym/iF4TS2yK9FdeRfxQ=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
path-browserify@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/path-browserify/-/path-browserify-0.0.1.tgz#e6c4ddd7ed3aa27c68a20cc4e50e1a4ee83bbc4a"
integrity sha512-BapA40NHICOS+USX9SN4tyhq+A2RrN/Ws5F0Z5aMHDp98Fl86lX8Oti8B7uN93L4Ifv4fHOEA+pQw87gmMO/lQ==
path-dirname@^1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/path-dirname/-/path-dirname-1.0.2.tgz#cc33d24d525e099a5388c0336c6e32b9160609e0"
integrity sha1-zDPSTVJeCZpTiMAzbG4yuRYGCeA=
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
path-exists@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/path-exists/-/path-exists-3.0.0.tgz#ce0ebeaa5f78cb18925ea7d810d7b59b010fd515"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-zg6+ql94yxiSXqfYENe1mwEP1RU=
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
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
path-is-absolute@^1.0.0:
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
version "1.0.1"
resolved "https://registry.yarnpkg.com/path-is-absolute/-/path-is-absolute-1.0.1.tgz#174b9268735534ffbc7ace6bf53a5a9e1b5c5f5f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-F0uSaHNVNP+8es5r9TpanhtcX18=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
path-is-inside@^1.0.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
version "1.0.2"
resolved "https://registry.yarnpkg.com/path-is-inside/-/path-is-inside-1.0.2.tgz#365417dede44430d1c11af61027facf074bdfc53"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-NlQX3t5EQw0cEa9hAn+s8HS9/FM=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
path-key@^2.0.0, path-key@^2.0.1:
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
version "2.0.1"
resolved "https://registry.yarnpkg.com/path-key/-/path-key-2.0.1.tgz#411cadb574c5a140d3a4b1910d40d80cc9f40b40"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-QRyttXTFoUDTpLGRDUDYDMn0C0A=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
path-parse@^1.0.6:
version "1.0.6"
resolved "https://registry.yarnpkg.com/path-parse/-/path-parse-1.0.6.tgz#d62dbb5679405d72c4737ec58600e9ddcf06d24c"
integrity sha512-GSmOT2EbHrINBf9SR7CDELwlJ8AENk3Qn7OikK4nFYAu3Ote2+JYNVvkpAEQm3/TLNEJFD/xZJjzyxg3KBWOzw==
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
path-to-regexp@0.1.7:
version "0.1.7"
resolved "https://registry.yarnpkg.com/path-to-regexp/-/path-to-regexp-0.1.7.tgz#df604178005f522f15eb4490e7247a1bfaa67f8c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-32BBeABfUi8V60SQ5yR6G/qmf4w=
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
path-type@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/path-type/-/path-type-2.0.0.tgz#f012ccb8415b7096fc2daa1054c3d72389594c73"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-8BLMuEFbcJb8LaoQVMPXI4lZTHM=
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:
pify "^2.0.0"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
path-type@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/path-type/-/path-type-3.0.0.tgz#cef31dc8e0a1a3bb0d105c0cd97cf3bf47f4e36f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-T2ZUsdZFHgA3u4e5PfPbjd7HDDpxPnQb5jN0SrDsjNSuVXHJqtwTnWqG0B1jZrgmJ/7lj1EmVIByWt1gxGkWvg==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
pify "^3.0.0"
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
pbkdf2@^3.0.3:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.0.17"
resolved "https://registry.yarnpkg.com/pbkdf2/-/pbkdf2-3.0.17.tgz#976c206530617b14ebb32114239f7b09336e93a6"
integrity sha512-U/il5MsrZp7mGg3mSQfn742na2T+1/vHDCG5/iTI3X9MKUuYUZVLQhyRsg06mCgDBTd57TxzgZt7P+fYfjRLtA==
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:
create-hash "^1.1.2"
create-hmac "^1.1.4"
ripemd160 "^2.0.1"
safe-buffer "^5.0.1"
sha.js "^2.4.8"
performance-now@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/performance-now/-/performance-now-2.1.0.tgz#6309f4e0e5fa913ec1c69307ae364b4b377c9e7b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Ywn04OX6kT7BxpMHrjZLSzd8nns=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
pify@^2.0.0:
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
version "2.3.0"
resolved "https://registry.yarnpkg.com/pify/-/pify-2.3.0.tgz#ed141a6ac043a849ea588498e7dca8b15330e90c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-7RQaasBDqEnqWISY59yosVMw6Qw=
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
pify@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/pify/-/pify-3.0.0.tgz#e5a4acd2c101fdf3d9a4d07f0dbc4db49dd28176"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-5aSs0sEB/fPZpNB/DbxNtJ3SgXY=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
pify@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/pify/-/pify-4.0.1.tgz#4b2cd25c50d598735c50292224fd8c6df41e3231"
integrity sha512-uB80kBFb/tfd68bVleG9T5GGsGPjJrLAUpR5PZIrhBnIaRTQRjqdJSsIKkOP6OAIFbj7GOrcudc5pNjZ+geV2g==
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
pinkie-promise@^2.0.0:
version "2.0.1"
resolved "https://registry.yarnpkg.com/pinkie-promise/-/pinkie-promise-2.0.1.tgz#2135d6dfa7a358c069ac9b178776288228450ffa"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-ITXW36ejWMBprJsXh3YogihFD/o=
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:
pinkie "^2.0.0"
pinkie@^2.0.0:
version "2.0.4"
resolved "https://registry.yarnpkg.com/pinkie/-/pinkie-2.0.4.tgz#72556b80cfa0d48a974e80e77248e80ed4f7f870"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-clVrgM+g1IqXToDnckjoDtT3+HA=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
pirates@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/pirates/-/pirates-4.0.1.tgz#643a92caf894566f91b2b986d2c66950a8e2fb87"
integrity sha512-WuNqLTbMI3tmfef2TKxlQmAiLHKtFhlsCZnPIpuv2Ow0RDVO8lfy1Opf4NUzlMXLjPl+Men7AuVdX6TA+s+uGA==
dependencies:
node-modules-regexp "^1.0.0"
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
pkg-dir@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/pkg-dir/-/pkg-dir-2.0.0.tgz#f6d5d1109e19d63edf428e0bd57e12777615334b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-9tXREJ4Z1j7fQo4L1X4Sd3YVM0s=
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:
find-up "^2.1.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
pkg-dir@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/pkg-dir/-/pkg-dir-3.0.0.tgz#2749020f239ed990881b1f71210d51eb6523bea3"
integrity sha512-/E57AYkoeQ25qkxMj5PBOVgF8Kiu/h7cYS30Z5+R7WaiCCBfLq58ZI/dSeaEKb9WVJV5n/03QwrN3IeWIFllvw==
dependencies:
find-up "^3.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
pn@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/pn/-/pn-1.1.0.tgz#e2f4cef0e219f463c179ab37463e4e1ecdccbafb"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-2qHaIQr2VLRFoxe2nASzsV6ef4yOOH+Fi9FBOVH6cqeSgUnoyySPZkxzLuzd+RYOQTRpROA0ztTMqxROKSb/nA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
portfinder@^1.0.20:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.20"
resolved "https://registry.yarnpkg.com/portfinder/-/portfinder-1.0.20.tgz#bea68632e54b2e13ab7b0c4775e9b41bf270e44a"
integrity sha512-Yxe4mTyDzTd59PZJY4ojZR8F+E5e97iq2ZOHPz3HDgSvYC5siNad2tLooQ5y5QHyQhc3xVqvyk/eNA3wuoa7Sw==
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:
async "^1.5.2"
debug "^2.2.0"
mkdirp "0.5.x"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
posix-character-classes@^0.1.0:
version "0.1.1"
resolved "https://registry.yarnpkg.com/posix-character-classes/-/posix-character-classes-0.1.1.tgz#01eac0fe3b5af71a2a6c02feabb8c1fef7e00eab"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-AerA/jta9xoqbAL+q7jB/vfgDqs=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
postcss-modules-extract-imports@^2.0.0:
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
version "2.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
resolved "https://registry.yarnpkg.com/postcss-modules-extract-imports/-/postcss-modules-extract-imports-2.0.0.tgz#818719a1ae1da325f9832446b01136eeb493cd7e"
integrity sha512-LaYLDNS4SG8Q5WAWqIJgdHPJrDDr/Lv775rMBFUbgjTz6j34lUznACHcdRWroPvXANP2Vj7yNK57vp9eFqzLWQ==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
postcss "^7.0.5"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
postcss-modules-local-by-default@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/postcss-modules-local-by-default/-/postcss-modules-local-by-default-3.0.2.tgz#e8a6561be914aaf3c052876377524ca90dbb7915"
integrity sha512-jM/V8eqM4oJ/22j0gx4jrp63GSvDH6v86OqyTHHUvk4/k1vceipZsaymiZ5PvocqZOl5SFHiFJqjs3la0wnfIQ==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
icss-utils "^4.1.1"
postcss "^7.0.16"
postcss-selector-parser "^6.0.2"
postcss-value-parser "^4.0.0"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
postcss-modules-scope@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/postcss-modules-scope/-/postcss-modules-scope-2.1.0.tgz#ad3f5bf7856114f6fcab901b0502e2a2bc39d4eb"
integrity sha512-91Rjps0JnmtUB0cujlc8KIKCsJXWjzuxGeT/+Q2i2HXKZ7nBUeF9YQTZZTNvHVoNYj1AthsjnGLtqDUE0Op79A==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
postcss "^7.0.6"
postcss-selector-parser "^6.0.0"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
postcss-modules-values@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/postcss-modules-values/-/postcss-modules-values-3.0.0.tgz#5b5000d6ebae29b4255301b4a3a54574423e7f10"
integrity sha512-1//E5jCBrZ9DmRX+zCtmQtRSV6PV42Ix7Bzj9GbwJceduuf7IqP8MgeTXuRDHOWj2m0VzZD5+roFWDuU8RQjcg==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
icss-utils "^4.0.0"
postcss "^7.0.6"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
postcss-selector-parser@^6.0.0, postcss-selector-parser@^6.0.2:
version "6.0.2"
resolved "https://registry.yarnpkg.com/postcss-selector-parser/-/postcss-selector-parser-6.0.2.tgz#934cf799d016c83411859e09dcecade01286ec5c"
integrity sha512-36P2QR59jDTOAiIkqEprfJDsoNrvwFei3eCqKd1Y0tUsBimsq39BLp7RD+JWny3WgB1zGhJX8XVePwm9k4wdBg==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
cssesc "^3.0.0"
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
indexes-of "^1.0.1"
uniq "^1.0.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
postcss-value-parser@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/postcss-value-parser/-/postcss-value-parser-4.0.0.tgz#99a983d365f7b2ad8d0f9b8c3094926eab4b936d"
integrity sha512-ESPktioptiSUchCKgggAkzdmkgzKfmp0EU8jXH+5kbIUB+unr0Y4CY9SRMvibuvYUBjNh1ACLbxqYNpdTQOteQ==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
postcss@^7.0.14, postcss@^7.0.16, postcss@^7.0.17, postcss@^7.0.5, postcss@^7.0.6:
version "7.0.17"
resolved "https://registry.yarnpkg.com/postcss/-/postcss-7.0.17.tgz#4da1bdff5322d4a0acaab4d87f3e782436bad31f"
integrity sha512-546ZowA+KZ3OasvQZHsbuEpysvwTZNGJv9EfyCQdsIDltPSWHAeTQ5fQy/Npi2ZDtLI3zs7Ps/p6wThErhm9fQ==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
chalk "^2.4.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
source-map "^0.6.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
supports-color "^6.1.0"
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
prelude-ls@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/prelude-ls/-/prelude-ls-1.1.2.tgz#21932a549f5e52ffd9a827f570e04be62a97da54"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-IZMqVJ9eUv/ZqCf1cOBL5iqX2lQ=
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
Upgrade prettier This commit updates our prettier version from `1.13` to `1.18`. Looks like software does get better over time! I like all of the changes. Test plan: `yarn test` passes. I've manually inspected the diffs.
2019-07-04 17:31:11 +00:00
prettier@^1.18.2:
version "1.18.2"
resolved "https://registry.yarnpkg.com/prettier/-/prettier-1.18.2.tgz#6823e7c5900017b4bd3acf46fe9ac4b4d7bda9ea"
integrity sha512-OeHeMc0JhFE9idD4ZdtNibzY0+TPHSpSSb9h8FqtP+YnoZZ1sl8Vc9b1sasjfymH3SonAF4QcA2+mzHPhMvIiw==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
pretty-format@^24.8.0:
version "24.8.0"
resolved "https://registry.yarnpkg.com/pretty-format/-/pretty-format-24.8.0.tgz#8dae7044f58db7cb8be245383b565a963e3c27f2"
integrity sha512-P952T7dkrDEplsR+TuY7q3VXDae5Sr7zmQb12JU/NDQa/3CH7/QW0yvqLcGN6jL+zQFKaoJcPc+yJxMTGmosqw==
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:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@jest/types" "^24.8.0"
ansi-regex "^4.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
ansi-styles "^3.2.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
react-is "^16.8.4"
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
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
private@^0.1.6:
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
version "0.1.8"
resolved "https://registry.yarnpkg.com/private/-/private-0.1.8.tgz#2381edb3689f7a53d653190060fcf822d2f368ff"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-VvivMrbvd2nKkiG38qjULzlc+4Vx4wm/whI9pQD35YrARNnhxeiRktSOhSukRLFNlzg6Br/cJPet5J/u19r/mg==
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
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
process-nextick-args@~2.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.0.1"
resolved "https://registry.yarnpkg.com/process-nextick-args/-/process-nextick-args-2.0.1.tgz#7820d9b16120cc55ca9ae7792680ae7dba6d7fe2"
integrity sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +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
process@^0.11.10:
version "0.11.10"
resolved "https://registry.yarnpkg.com/process/-/process-0.11.10.tgz#7332300e840161bda3e69a1d1d91a7d4bc16f182"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-czIwDoQBYb2j5podHZGn1LwW8YI=
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
progress@^2.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.0.3"
resolved "https://registry.yarnpkg.com/progress/-/progress-2.0.3.tgz#7e8cf8d8f5b8f239c1bc68beb4eb78567d572ef8"
integrity sha512-7PiHtLll5LdnKIMw100I+8xJXR5gW2QwWYkT6iJva0bXitZKa/XMrSbdmg3r2Xnaidz9Qumd0VPaMrZlF9V9sA==
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
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
promise-inflight@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/promise-inflight/-/promise-inflight-1.0.1.tgz#98472870bf228132fcbdd868129bad12c3c029e3"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-mEcocL8igTL8vdhoEputEsPAKeM=
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
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
promise-polyfill@^7.1.1:
version "7.1.2"
resolved "https://registry.yarnpkg.com/promise-polyfill/-/promise-polyfill-7.1.2.tgz#ab05301d8c28536301622d69227632269a70ca3b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-FuEc12/eKqqoRYIGBrUptCBRhobL19PS2U31vMNTfyck1FxPyMfgsXyW4Mav85y/ZN1hop3hOwRlUDok23oYfQ==
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
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
promise@8.0.3:
version "8.0.3"
resolved "https://registry.yarnpkg.com/promise/-/promise-8.0.3.tgz#f592e099c6cddc000d538ee7283bb190452b0bf6"
integrity sha512-HeRDUL1RJiLhyA0/grn+PTShlBAcLuh/1BJGtrvjwbvRDCTLLMEz9rOGCV+R3vHY4MixIuoMEd9Yq/XvsTPcjw==
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:
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
asap "~2.0.6"
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
promise@^7.1.1:
version "7.3.1"
resolved "https://registry.yarnpkg.com/promise/-/promise-7.3.1.tgz#064b72602b18f90f29192b8b1bc418ffd1ebd3bf"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-nolQXZ/4L+bP/UGlkfaIujX9BKxGwmQ9OT4mOt5yvy8iK1h3wqTEJCijzGANTCCl9nWjY41juyAn2K3Q1hLLTg==
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:
asap "~2.0.3"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
prompts@^2.0.1:
version "2.1.0"
resolved "https://registry.yarnpkg.com/prompts/-/prompts-2.1.0.tgz#bf90bc71f6065d255ea2bdc0fe6520485c1b45db"
integrity sha512-+x5TozgqYdOwWsQFZizE/Tra3fKvAoy037kOyU6cgz84n8f6zxngLOV4O32kTwt9FcLCxAqw0P/c8rOr9y+Gfg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
kleur "^3.0.2"
sisteransi "^1.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
prop-types-exact@^1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/prop-types-exact/-/prop-types-exact-1.2.0.tgz#825d6be46094663848237e3925a98c6e944e9869"
integrity sha512-K+Tk3Kd9V0odiXFP9fwDHUYRyvK3Nun3GVyPapSIs5OBkITAm15W0CPFD/YKTkMUAbc0b9CUwRQp2ybiBIq+eA==
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
has "^1.0.3"
object.assign "^4.1.0"
reflect.ownkeys "^0.2.0"
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
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
prop-types@^15.5.6, prop-types@^15.6.0, prop-types@^15.6.2, prop-types@^15.7.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
version "15.7.2"
resolved "https://registry.yarnpkg.com/prop-types/-/prop-types-15.7.2.tgz#52c41e75b8c87e72b9d9360e0206b99dcbffa6c5"
integrity sha512-8QQikdH7//R2vurIJSutZ1smHYTcLpRWEOlHnzcWHmBYrOGUysKwSsrC89BCiFj3CbrfJ/nXFdJepOVrY1GCHQ==
dependencies:
loose-envify "^1.4.0"
object-assign "^4.1.1"
react-is "^16.8.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
proxy-addr@~2.0.5:
version "2.0.5"
resolved "https://registry.yarnpkg.com/proxy-addr/-/proxy-addr-2.0.5.tgz#34cbd64a2d81f4b1fd21e76f9f06c8a45299ee34"
integrity sha512-t/7RxHXPH6cJtP0pRG6smSr9QJidhB+3kXu0KgXnbGYMgzEnUxRQ4/LDdfOwZEMyIh3/xHb8PX3t+lfL9z+YVQ==
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
dependencies:
forwarded "~0.1.2"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
ipaddr.js "1.9.0"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +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
prr@~1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/prr/-/prr-1.0.1.tgz#d3fc114ba06995a45ec6893f484ceb1d78f5f476"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-0/wRS6BplaRexok/SEzrHXj19HY=
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
pseudomap@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/pseudomap/-/pseudomap-1.0.2.tgz#f052a28da70e618917ef0a8ac34c1ae5a68286b3"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-8FKijacOYYkX7wqKw0wa5aaChrM=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
psl@^1.1.24, psl@^1.1.28:
version "1.2.0"
resolved "https://registry.yarnpkg.com/psl/-/psl-1.2.0.tgz#df12b5b1b3a30f51c329eacbdef98f3a6e136dc6"
integrity sha512-GEn74ZffufCmkDDLNcl3uuyF/aSD6exEyh1v/ZSdAomB82t6G9hzJVRx0jBmLDW+VfZqks3aScmMw9DszwUalA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
public-encrypt@^4.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "4.0.3"
resolved "https://registry.yarnpkg.com/public-encrypt/-/public-encrypt-4.0.3.tgz#4fcc9d77a07e48ba7527e7cbe0de33d0701331e0"
integrity sha512-zVpa8oKZSz5bTMTFClc1fQOnyyEzpl5ozpi1B5YcvBrdohMjH2rfsBtyXcuNuwjsDIXmBYlF2N5FlJYhR29t8Q==
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:
bn.js "^4.1.0"
browserify-rsa "^4.0.0"
create-hash "^1.1.0"
parse-asn1 "^5.0.0"
randombytes "^2.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
safe-buffer "^5.1.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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
pump@^2.0.0:
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
version "2.0.1"
resolved "https://registry.yarnpkg.com/pump/-/pump-2.0.1.tgz#12399add6e4cf7526d973cbc8b5ce2e2908b3909"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-ruPMNRkN3MHP1cWJc9OWr+T/xDP0jhXYCLfJcBuX54hhfIBnaQmAUMfDcG4DM5UMWByBbJY69QSphm3jtDKIkA==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
end-of-stream "^1.1.0"
once "^1.3.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
pump@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/pump/-/pump-3.0.0.tgz#b4a2116815bde2f4e1ea602354e8c75565107a64"
integrity sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==
dependencies:
end-of-stream "^1.1.0"
once "^1.3.1"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
pumpify@^1.3.3:
version "1.5.1"
resolved "https://registry.yarnpkg.com/pumpify/-/pumpify-1.5.1.tgz#36513be246ab27570b1a374a5ce278bfd74370ce"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-oClZI37HvuUJJxSKKrC17bZ9Cu0ZYhEAGPsPUy9KlMUmv9dKX2o77RUmq7f3XjIxbwyGwYzbzQ1L2Ks8sIradQ==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
duplexify "^3.6.0"
inherits "^2.0.3"
pump "^2.0.0"
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
punycode@1.3.2:
version "1.3.2"
resolved "https://registry.yarnpkg.com/punycode/-/punycode-1.3.2.tgz#9653a036fb7c1ee42342f2325cceefea3926c48d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-llOgNvt8HuQjQvIyXM7v6jkmxI0=
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
punycode@^1.2.4, punycode@^1.4.1:
version "1.4.1"
resolved "https://registry.yarnpkg.com/punycode/-/punycode-1.4.1.tgz#c0d5a63b2718800ad8e1eb0fa5269c84dd41845e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-wNWmOycYgArY4esPpSachN1BhF4=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
punycode@^2.1.0, punycode@^2.1.1:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
version "2.1.1"
resolved "https://registry.yarnpkg.com/punycode/-/punycode-2.1.1.tgz#b58b010ac40c22c5657616c8d2c2c02c7bf479ec"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
qs@6.7.0:
version "6.7.0"
resolved "https://registry.yarnpkg.com/qs/-/qs-6.7.0.tgz#41dc1a015e3d581f1621776be31afb2876a9b1bc"
integrity sha512-VCdBRNFTX1fyE7Nb6FYoURo/SPe62QCaAyzJvUjwRaIsc+NePBEniHlvxFmmX56+HZphIGtV0XeCirBtpDrTyQ==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
qs@~6.5.2:
version "6.5.2"
resolved "https://registry.yarnpkg.com/qs/-/qs-6.5.2.tgz#cb3ae806e8740444584ef154ce8ee98d403f3e36"
integrity sha512-N5ZAX4/LxJmF+7wN74pUD6qAh9/wnvdQcjq9TZjevvXzSUo7bfmw91saqMjzGS2xq91/odN2dW/WOl7qQHNDGA==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
query-string@^4.2.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
version "4.3.4"
resolved "https://registry.yarnpkg.com/query-string/-/query-string-4.3.4.tgz#bbb693b9ca915c232515b228b1a02b609043dbeb"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-u7aTucqRXCMlFbIosaArYJBD2+s=
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:
object-assign "^4.1.0"
strict-uri-encode "^1.0.0"
querystring-es3@^0.2.0:
version "0.2.1"
resolved "https://registry.yarnpkg.com/querystring-es3/-/querystring-es3-0.2.1.tgz#9ec61f79049875707d69414596fd907a4d711e73"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-nsYfeQSYdXB9aUFFlv2Qek1xHnM=
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
querystring@0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/querystring/-/querystring-0.2.0.tgz#b209849203bb25df820da756e747005878521620"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-sgmEkgO7Jd+CDadW50cAWHhSFiA=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
querystringify@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/querystringify/-/querystringify-2.1.1.tgz#60e5a5fd64a7f8bfa4d2ab2ed6fdf4c85bad154e"
integrity sha512-w7fLxIRCRT7U8Qu53jQnJyPkYZIaR4n5151KMfcJlO/A9397Wxb1amJvROTK6TOnp7PfoAmg/qXiNHI+08jRfA==
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
raf@3.4.1, raf@^3.4.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.4.1"
resolved "https://registry.yarnpkg.com/raf/-/raf-3.4.1.tgz#0742e99a4a6552f445d73e3ee0328af0ff1ede39"
integrity sha512-Sq4CW4QhwOHE8ucn6J34MqtZCeWFP2aQSmrlroYgqAV1PjStIhJXxYuTgUIfkEk7zTLjmIjLmU5q+fbD1NnOJA==
dependencies:
performance-now "^2.1.0"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
railroad-diagrams@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/railroad-diagrams/-/railroad-diagrams-1.0.0.tgz#eb7e6267548ddedfb899c1b90e57374559cddb7e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-635iZ1SN3t+4mcG5Dlc3RVnN234=
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
Port skeleton of Odyssey frontend (#1132) This commit integrates an bare skeleton of the odyssey frontend that we implemented in the [odyssey-hackathon] repository. You can see the working frontend that we are trying to port over at [sourcecred.io/odyssey-hackathon/][scio]. The prototype in the other repository has some tooling choices which are incompatible/redundant with decisions in our codebase (sass vs aphrodite), and requires some tools not yet present here (svg-react-loader). This commit includes the build and integration work needed to port the prototype frontend into mainline SourceCred. The frontend scaffold isn't yet integrated with any "real" Odyssey data. One potential issue: right now, every page that is rendered from the SourceCred homepage is contained within a [homepage/Page], meaning that it has full SourceCred website styling, along with the SourceCred website header. The [application][scio] also has a header. Currently, I work around this by having the Odyssey UI cover up the base header (via absolute positioning), which works but is hacky. We can consider more principled solutions: - Finding a way to specify routes which aren't contained by [homepage/Page]; maybe by adding a new top-level route [here][route-alternative]. - Unify the headers for the Odyssey viewer and the page as a whole (sounds like inappropriate entanglement?) - Have a website header and also an application header (sounds ugly?) [homepage/Page]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/Page.js [route-alternative]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/createRoutes.js#L17 Test plan: Run `yarn start`, and then navigate to `localhost:8080/odyssey/`. observe that a working website is displayed, and that the cred logo next to the word "SourceCred" is loaded properly (i.e. svg-react-loader is integrated properly). Observe that there are no build/compile errors from either `yarn start` or `yarn build`. Also, observe that the UI looks passably nice, and that if the number of elements in the entity lists is larger than can be displayed, the sidebar pane scrolls independently. The UI was tested in both Chrome and Firefox. [odyssey-hackathon]: https://github.com/sourcecred/odyssey-hackathon [scio]: https://sourcecred.io/odyssey-hackathon/ Thanks to @jmnemo, as the implementation is based on [his work]. [his work]: https://github.com/jmnemo/hackathon-event/
2019-05-06 15:15:39 +00:00
ramda@0.21.0:
version "0.21.0"
resolved "https://registry.yarnpkg.com/ramda/-/ramda-0.21.0.tgz#a001abedb3ff61077d4ff1d577d44de77e8d0a35"
integrity sha1-oAGr7bP/YQd9T/HVd9RN536NCjU=
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
ramda@^0.26:
version "0.26.1"
resolved "https://registry.yarnpkg.com/ramda/-/ramda-0.26.1.tgz#8d41351eb8111c55353617fc3bbffad8e4d35d06"
integrity sha512-hLWjpy7EnsDBb0p+Z3B7rPi3GDeRG5ZtiI33kJhTt+ORCd38AbAIjB/9zRIUoeTbE/AVX5ZkU7m6bznsvrf8eQ==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
randexp@0.4.6:
version "0.4.6"
resolved "https://registry.yarnpkg.com/randexp/-/randexp-0.4.6.tgz#e986ad5e5e31dae13ddd6f7b3019aa7c87f60ca3"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-80WNmd9DA0tmZrw9qQa62GPPWfuXJknrmVmLcxvq4uZBdYqb1wYoKTmnlGUchvVWe0XiLupYkBoXVOxz3C8DYQ==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
discontinuous-range "1.0.0"
ret "~0.1.10"
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
randombytes@^2.0.0, randombytes@^2.0.1, randombytes@^2.0.5:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.1.0"
resolved "https://registry.yarnpkg.com/randombytes/-/randombytes-2.1.0.tgz#df6f84372f0270dc65cdf6291349ab7a473d4f2a"
integrity sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==
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:
safe-buffer "^5.1.0"
randomfill@^1.0.3:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.4"
resolved "https://registry.yarnpkg.com/randomfill/-/randomfill-1.0.4.tgz#c92196fc86ab42be983f1bf31778224931d61458"
integrity sha512-87lcbR8+MhcWcUiQ+9e+Rwx8MyR2P7qnt15ynUlbm3TU/fjbgz4GsvfSUDTemtCCtVCqb4ZcEFlyPNTh9bBTLw==
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:
randombytes "^2.0.5"
safe-buffer "^5.1.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
range-parser@^1.2.1, range-parser@~1.2.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.2.1"
resolved "https://registry.yarnpkg.com/range-parser/-/range-parser-1.2.1.tgz#3cf37023d199e1c24d1a55b84800c2f3e6468031"
integrity sha512-Hrgsx+orqoygnmhFbKaHE6c296J+HTAQXoxEF6gNupROmmGJRoyzfG3ccAveqCBrwr/2yxQ5BVd/GTl5agOwSg==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
raw-body@2.4.0:
version "2.4.0"
resolved "https://registry.yarnpkg.com/raw-body/-/raw-body-2.4.0.tgz#a1ce6fb9c9bc356ca52e89256ab59059e13d0332"
integrity sha512-4Oz8DUIwdvoa5qMJelxipzi/iJIi40O5cGV1wNYp5hvZP8ZN0T+jiNkL0QepXs+EsQ9XJ8ipEDoiH70ySUJP3Q==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
bytes "3.1.0"
http-errors "1.7.2"
iconv-lite "0.4.24"
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
unpipe "1.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
rc@^1.2.7:
version "1.2.8"
resolved "https://registry.yarnpkg.com/rc/-/rc-1.2.8.tgz#cd924bf5200a075b83c188cd6b9e211b7fc0d3ed"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
deep-extend "^0.6.0"
ini "~1.3.0"
minimist "^1.2.0"
strip-json-comments "~2.0.1"
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
react-dev-utils@^5.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "5.0.3"
resolved "https://registry.yarnpkg.com/react-dev-utils/-/react-dev-utils-5.0.3.tgz#92f97668f03deb09d7fa11ea288832a8c756e35e"
integrity sha512-Mvs6ofsc2xTjeZIrMaIfbXfsPVrbdVy/cVqq6SAacnqfMlcBpDuivhWZ1ODGeJ8HgmyWTLH971PYjj/EPCDVAw==
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:
address "1.0.3"
babel-code-frame "6.26.0"
chalk "1.1.3"
cross-spawn "5.1.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
detect-port-alt "1.1.6"
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
escape-string-regexp "1.0.5"
filesize "3.5.11"
global-modules "1.0.0"
gzip-size "3.0.0"
inquirer "3.3.0"
is-root "1.0.0"
opn "5.2.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
react-error-overlay "^4.0.1"
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
recursive-readdir "2.2.1"
shell-quote "1.6.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
sockjs-client "1.1.5"
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
strip-ansi "3.0.1"
text-table "0.2.0"
Upgrade react and react-dom to latest (#541) Test plan: `yarn travis --full`, as well as thorough manual frontend testing
2018-07-27 20:27:19 +00:00
react-dom@^16.4.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "16.8.6"
resolved "https://registry.yarnpkg.com/react-dom/-/react-dom-16.8.6.tgz#71d6303f631e8b0097f56165ef608f051ff6e10f"
integrity sha512-1nL7PIq9LTL3fthPqwkvr2zY7phIPjYrT0jp4HjyEQrEROnw4dG41VVwi/wfoCneoleqrNX7iAD+pXebJZwrwA==
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:
loose-envify "^1.1.0"
object-assign "^4.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
prop-types "^15.6.2"
scheduler "^0.13.6"
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
react-error-overlay@^4.0.1:
version "4.0.1"
resolved "https://registry.yarnpkg.com/react-error-overlay/-/react-error-overlay-4.0.1.tgz#417addb0814a90f3a7082eacba7cee588d00da89"
integrity sha512-xXUbDAZkU08aAkjtUvldqbvI04ogv+a1XdHxvYuHPYKIVk/42BIOD0zSKTHAWV4+gDy3yGm283z2072rA2gdtw==
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
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
react-icons@^3.7.0:
version "3.7.0"
resolved "https://registry.yarnpkg.com/react-icons/-/react-icons-3.7.0.tgz#64fe46231fabfeea27895edeae6c3b78114b8c8f"
integrity sha512-7MyPwjIhuyW0D2N3s4DEd0hGPGFf0sK+IIRKhc1FvSpZNVmnUoGvHbmAwzGJU+3my+fvihVWgwU5SDtlAri56Q==
dependencies:
camelcase "^5.0.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
react-is@^16.8.1, react-is@^16.8.4, react-is@^16.8.6:
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
version "16.8.6"
resolved "https://registry.yarnpkg.com/react-is/-/react-is-16.8.6.tgz#5bbc1e2d29141c9fbdfed456343fe2bc430a6a16"
integrity sha512-aUk3bHfZ2bRSVFFbbeVS4i+lNPZr3/WM5jT2J5omUVV1zzcs1nAaf3l51ctA5FFvCRbhrH0bdAsRRQddFJZPtA==
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
react-lifecycles-compat@^3.0.4:
version "3.0.4"
resolved "https://registry.yarnpkg.com/react-lifecycles-compat/-/react-lifecycles-compat-3.0.4.tgz#4f1a273afdfc8f3488a8c516bfda78f872352362"
integrity sha512-fBASbA6LnOU9dOU2eW7aQ8xmYBSXUIWr+UmF9b1efZBazGNO+rcXT/icdKnYm2pTwcRylVUYwW7H1PHfLekVzA==
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
react-markdown@^4.0.8:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "4.1.0"
resolved "https://registry.yarnpkg.com/react-markdown/-/react-markdown-4.1.0.tgz#7fdf840ecbabc803f28156f7411c726b58f25a73"
integrity sha512-EOHsEAN+aoP8UVz7vTHx6Z63GJfhrO9KItKlfsiBtVVS9tmSWtUaBTw73+2SObrWiOiE2Cs9qUBL7ORsvVhOrA==
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
dependencies:
html-to-react "^1.3.4"
mdast-add-list-metadata "1.0.1"
prop-types "^15.7.2"
remark-parse "^5.0.0"
unified "^6.1.5"
unist-util-visit "^1.3.0"
xtend "^4.0.1"
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
react-resize-detector@^2.3.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/react-resize-detector/-/react-resize-detector-2.3.0.tgz#57bad1ae26a28a62a2ddb678ba6ffdf8fa2b599c"
integrity sha512-oCAddEWWeFWYH5FAcHdBYcZjAw9fMzRUK9sWSx6WvSSOPVRxcHd5zTIGy/mOus+AhN/u6T4TMiWxvq79PywnJQ==
dependencies:
lodash.debounce "^4.0.8"
lodash.throttle "^4.1.1"
prop-types "^15.6.0"
resize-observer-polyfill "^1.5.0"
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
react-router@3.2.1:
version "3.2.1"
resolved "https://registry.yarnpkg.com/react-router/-/react-router-3.2.1.tgz#b9a3279962bdfbe684c8bd0482b81ef288f0f244"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-SXkhC0nr3G0ltzVU07IN8jYl0bB6FsrDIqlLC9dK3SITXqyTJyM7yhXlUqs89w3Nqi5OkXsfRUeHX+P874HQrg==
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
dependencies:
create-react-class "^15.5.1"
history "^3.0.0"
hoist-non-react-statics "^2.3.1"
invariant "^2.2.1"
loose-envify "^1.2.0"
prop-types "^15.5.6"
warning "^3.0.0"
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
react-smooth@^1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/react-smooth/-/react-smooth-1.0.2.tgz#f7a2d932ece8db898646078c3c97f3e9533e0486"
integrity sha512-pIGzL1g9VGAsRsdZQokIK0vrCkcdKtnOnS1gyB2rrowdLy69lNSWoIjCTWAfgbiYvria8tm5hEZqj+jwXMkV4A==
dependencies:
lodash "~4.17.4"
prop-types "^15.6.0"
raf "^3.4.0"
react-transition-group "^2.5.0"
Standardize on Enzyme shallow rendering (#104) Summary: This commit moves our existing frontend tests to use Enzyme’s shallow rendering API <http://airbnb.io/enzyme/docs/api/shallow.html>. The benefit over also using `react-test-renderer` is simply consistency (the two are functionally equivalent); the benefits over `mount` are that subcomponents cannot contaminate the test state (i.e., you’re only testing one component at a time), that the resulting snapshots are more readable because the root props are not shown, and that the implementation is more efficient. This is a follow-up to #102. In a case where we actually need a full DOM tree, we should still feel free to use `mount`, but we haven’t needed that yet. Test Plan: Verify that the new `ContributionList.test.js.snap` represents the same data as the old one. wchargin-branch: standardize-enzyme-shallow
2018-03-22 01:28:06 +00:00
react-test-renderer@^16.0.0-0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "16.8.6"
resolved "https://registry.yarnpkg.com/react-test-renderer/-/react-test-renderer-16.8.6.tgz#188d8029b8c39c786f998aa3efd3ffe7642d5ba1"
integrity sha512-H2srzU5IWYT6cZXof6AhUcx/wEyJddQ8l7cLM/F7gDXYyPr4oq+vCIxJYXVGhId1J706sqziAjuOEjyNkfgoEw==
Begin work on contributions and adapters (#93) Summary: This commit begins to extend the artifact editor to display contributions. To display contributions from arbitrary plugins, we need to communicate with those plugins somehow. We do so via an adapter interface that plugins implement; included in this commit is an implementation of this interface for the GitHub plugin (partially: we punt on rendering). This includes a snapshot test. The snapshot format is designed to be human-readable and -auditable so that it can serve as documentation. Test Plan: Run the application with `yarn start`. Then, fetch a graph and watch as its contributions appear in the view. wchargin-branch: contributions-and-adapters
2018-03-20 21:26:02 +00:00
dependencies:
object-assign "^4.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
prop-types "^15.6.2"
react-is "^16.8.6"
scheduler "^0.13.6"
Begin work on contributions and adapters (#93) Summary: This commit begins to extend the artifact editor to display contributions. To display contributions from arbitrary plugins, we need to communicate with those plugins somehow. We do so via an adapter interface that plugins implement; included in this commit is an implementation of this interface for the GitHub plugin (partially: we punt on rendering). This includes a snapshot test. The snapshot format is designed to be human-readable and -auditable so that it can serve as documentation. Test Plan: Run the application with `yarn start`. Then, fetch a graph and watch as its contributions appear in the view. wchargin-branch: contributions-and-adapters
2018-03-20 21:26:02 +00:00
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
react-transition-group@^2.5.0:
version "2.9.0"
resolved "https://registry.yarnpkg.com/react-transition-group/-/react-transition-group-2.9.0.tgz#df9cdb025796211151a436c69a8f3b97b5b07c8d"
integrity sha512-+HzNTCHpeQyl4MJ/bdE0u6XRMe9+XG/+aL4mCxVN4DnPBQ0/5bfHWPDuOZUzYdMj94daZaZdCCc1Dzt9R/xSSg==
dependencies:
dom-helpers "^3.4.0"
loose-envify "^1.4.0"
prop-types "^15.6.2"
react-lifecycles-compat "^3.0.4"
Upgrade react and react-dom to latest (#541) Test plan: `yarn travis --full`, as well as thorough manual frontend testing
2018-07-27 20:27:19 +00:00
react@^16.4.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "16.8.6"
resolved "https://registry.yarnpkg.com/react/-/react-16.8.6.tgz#ad6c3a9614fd3a4e9ef51117f54d888da01f2bbe"
integrity sha512-pC0uMkhLaHm11ZSJULfOBqV4tIZkx87ZLvbbQYunNixAAvjnC+snJCg0XQXn9VIsttVsbZP/H/ewzgsd5fxKXw==
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:
loose-envify "^1.1.0"
object-assign "^4.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
prop-types "^15.6.2"
scheduler "^0.13.6"
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
read-pkg-up@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/read-pkg-up/-/read-pkg-up-2.0.0.tgz#6b72a8048984e0c41e79510fd5e9fa99b3b549be"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-a3KoBImE4MQeeVEP1en6mbO1Sb4=
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:
find-up "^2.0.0"
read-pkg "^2.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
read-pkg-up@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/read-pkg-up/-/read-pkg-up-4.0.0.tgz#1b221c6088ba7799601c808f91161c66e58f8978"
integrity sha512-6etQSH7nJGsK0RbG/2TeDzZFa8shjQ1um+SwQQ5cwKy0dhSXdOncEhb1CPpvQG4h7FyOV6EB6YlV0yJvZQNAkA==
dependencies:
find-up "^3.0.0"
read-pkg "^3.0.0"
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
read-pkg@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/read-pkg/-/read-pkg-2.0.0.tgz#8ef1c0623c6a6db0dc6713c4bfac46332b2368f8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-jvHAYjxqbbDcZxPEv6xGMysjaPg=
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:
load-json-file "^2.0.0"
normalize-package-data "^2.3.2"
path-type "^2.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
read-pkg@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/read-pkg/-/read-pkg-3.0.0.tgz#9cbc686978fee65d16c00e2b19c237fcf6e38389"
integrity sha1-nLxoaXj+5l0WwA4rGcI3/Pbjg4k=
dependencies:
load-json-file "^4.0.0"
normalize-package-data "^2.3.2"
path-type "^3.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
"readable-stream@1 || 2", readable-stream@^2.0.0, readable-stream@^2.0.1, readable-stream@^2.0.2, readable-stream@^2.0.6, readable-stream@^2.1.5, readable-stream@^2.2.2, readable-stream@^2.3.3, readable-stream@^2.3.6, readable-stream@~2.3.6:
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
version "2.3.6"
resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-2.3.6.tgz#b11c27d88b8ff1fbe070643cf94b0c79ae1b0aaf"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-tQtKA9WIAhBF3+VLAseyMqZeBjW0AHJoxOtYqSUZNJxauErmLbVm2FW1y+J/YA9dUrAC39ITejlZWhVIwawkKw==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
core-util-is "~1.0.0"
inherits "~2.0.3"
isarray "~1.0.0"
process-nextick-args "~2.0.0"
safe-buffer "~5.1.1"
string_decoder "~1.1.1"
util-deprecate "~1.0.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
readable-stream@^3.0.6, readable-stream@^3.1.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.4.0"
resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-3.4.0.tgz#a51c26754658e0a3c21dbf59163bd45ba6f447fc"
integrity sha512-jItXPLmrSR8jmTRmRWJXCnGJsfy85mB3Wd/uINMXA65yrnFo0cPClFIUWzo2najVNSl+mx7/4W8ttlLWJe99pQ==
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
dependencies:
inherits "^2.0.3"
string_decoder "^1.1.1"
util-deprecate "^1.0.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
readdirp@^2.2.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.2.1"
resolved "https://registry.yarnpkg.com/readdirp/-/readdirp-2.2.1.tgz#0e87622a3325aa33e892285caf8b4e846529a525"
integrity sha512-1JU/8q+VgFZyxwrJ+SVIOsh+KywWGpds3NTqikiKpDMZWScmAYyKIgqkO+ARvNWJfXeXR1zxz7aHF4u4CyH6vQ==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
graceful-fs "^4.1.11"
micromatch "^3.1.10"
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
readable-stream "^2.0.2"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
realpath-native@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/realpath-native/-/realpath-native-1.1.0.tgz#2003294fea23fb0672f2476ebe22fcf498a2d65c"
integrity sha512-wlgPA6cCIIg9gKz0fgAPjnzh4yR/LnXovwuo9hvyGvx3h8nX4+/iLZplfUWasXpqD8BdnGnP5njOFjkUwPzvjA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
util.promisify "^1.0.0"
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
recharts-scale@^0.4.2:
version "0.4.2"
resolved "https://registry.yarnpkg.com/recharts-scale/-/recharts-scale-0.4.2.tgz#b66315d985cd9b80d5f7d977a5aab9a305abc354"
integrity sha512-p/cKt7j17D1CImLgX2f5+6IXLbRHGUQkogIp06VUoci/XkhOQiGSzUrsD1uRmiI7jha4u8XNFOjkHkzzBPivMg==
dependencies:
decimal.js-light "^2.4.1"
recharts@^1.6.2:
version "1.6.2"
resolved "https://registry.yarnpkg.com/recharts/-/recharts-1.6.2.tgz#4ced884f04b680e8dac5d3e109f99b0e7cfb9b0f"
integrity sha512-NqVN8Hq5wrrBthTxQB+iCnZjup1dc+AYRIB6Q9ck9UjdSJTt4PbLepGpudQEYJEN5iIpP/I2vThC4uiTJa7xUQ==
dependencies:
classnames "^2.2.5"
core-js "^2.5.1"
d3-interpolate "^1.3.0"
d3-scale "^2.1.0"
d3-shape "^1.2.0"
lodash "^4.17.5"
prop-types "^15.6.0"
react-resize-detector "^2.3.0"
react-smooth "^1.0.0"
recharts-scale "^0.4.2"
reduce-css-calc "^1.3.0"
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
recursive-readdir@2.2.1:
version "2.2.1"
resolved "https://registry.yarnpkg.com/recursive-readdir/-/recursive-readdir-2.2.1.tgz#90ef231d0778c5ce093c9a48d74e5c5422d13a99"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-kO8jHQd4xc4JPJpI105cVCLROpk=
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:
minimatch "3.0.3"
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
reduce-css-calc@^1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/reduce-css-calc/-/reduce-css-calc-1.3.0.tgz#747c914e049614a4c9cfbba629871ad1d2927716"
integrity sha1-dHyRTgSWFKTJz7umKYca0dKSdxY=
dependencies:
balanced-match "^0.4.2"
math-expression-evaluator "^1.2.14"
reduce-function-call "^1.0.1"
reduce-function-call@^1.0.1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/reduce-function-call/-/reduce-function-call-1.0.2.tgz#5a200bf92e0e37751752fe45b0ab330fd4b6be99"
integrity sha1-WiAL+S4ON3UXUv5FsKszD9S2vpk=
dependencies:
balanced-match "^0.4.2"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
reflect.ownkeys@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/reflect.ownkeys/-/reflect.ownkeys-0.2.0.tgz#749aceec7f3fdf8b63f927a04809e90c5c0b3460"
integrity sha1-dJrO7H8/34tj+SegSAnpDFwLNGA=
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
regenerate-unicode-properties@^8.0.2:
version "8.1.0"
resolved "https://registry.yarnpkg.com/regenerate-unicode-properties/-/regenerate-unicode-properties-8.1.0.tgz#ef51e0f0ea4ad424b77bf7cb41f3e015c70a3f0e"
integrity sha512-LGZzkgtLY79GeXLm8Dp0BVLdQlWICzBnJz/ipWUgo59qBaZ+BHtq51P2q1uVZlppMuUAT37SDk39qUbjTWB7bA==
dependencies:
regenerate "^1.4.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
regenerate@^1.4.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.4.0"
resolved "https://registry.yarnpkg.com/regenerate/-/regenerate-1.4.0.tgz#4a856ec4b56e4077c557589cae85e7a4c8869a11"
integrity sha512-1G6jJVDWrt0rK99kBjvEtziZNCICAuvIPkSiUFIQxVP06RCVpq3dmDo2oi6ABpYaDYaTRr67BEhL8r1wgEZZKg==
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
regenerator-runtime@^0.13.2:
version "0.13.2"
resolved "https://registry.yarnpkg.com/regenerator-runtime/-/regenerator-runtime-0.13.2.tgz#32e59c9a6fb9b1a4aff09b4930ca2d4477343447"
integrity sha512-S/TQAZJO+D3m9xeN1WTI8dLKBBiRgXBlTJvbWjCThHWZj9EvHK70Ff50/tYj2J/fvBY6JtFVwRuazHN2E7M9BA==
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
regenerator-transform@^0.14.0:
version "0.14.0"
resolved "https://registry.yarnpkg.com/regenerator-transform/-/regenerator-transform-0.14.0.tgz#2ca9aaf7a2c239dd32e4761218425b8c7a86ecaf"
integrity sha512-rtOelq4Cawlbmq9xuMR5gdFmv7ku/sFoB7sRiywx7aq53bc52b4j6zvH7Te1Vt/X2YveDKnCGUbioieU7FEL3w==
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:
private "^0.1.6"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
regex-not@^1.0.0, regex-not@^1.0.2:
version "1.0.2"
resolved "https://registry.yarnpkg.com/regex-not/-/regex-not-1.0.2.tgz#1f4ece27e00b0b65e0247a6810e6a85d83a5752c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-J6SDjUgDxQj5NusnOtdFxDwN/+HWykR8GELwctJ7mdqhcyy1xEc4SRFHUXvxTp661YaVKAjfRLZ9cCqS6tn32A==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
extend-shallow "^3.0.2"
safe-regex "^1.1.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
regexp-tree@^0.1.6:
version "0.1.11"
resolved "https://registry.yarnpkg.com/regexp-tree/-/regexp-tree-0.1.11.tgz#c9c7f00fcf722e0a56c7390983a7a63dd6c272f3"
integrity sha512-7/l/DgapVVDzZobwMCCgMlqiqyLFJ0cduo/j+3BcDJIB+yJdsYCfKuI3l/04NV+H/rfNRdPIDbXNZHM9XvQatg==
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
regexpp@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/regexpp/-/regexpp-2.0.1.tgz#8d19d31cf632482b589049f8281f93dbcba4d07f"
integrity sha512-lv0M6+TkDVniA3aD1Eg0DVpfU/booSu7Eev3TDO/mZKHBfVjgCGTV4t4buppESEYDtkArYFOxTJWv6S5C+iaNw==
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
regexpu-core@^4.5.4:
version "4.5.4"
resolved "https://registry.yarnpkg.com/regexpu-core/-/regexpu-core-4.5.4.tgz#080d9d02289aa87fe1667a4f5136bc98a6aebaae"
integrity sha512-BtizvGtFQKGPUcTy56o3nk1bGRp4SZOTYrDtGNlqCQufptV5IkkLN6Emw+yunAJjzf+C9FQFtvq7IoA3+oMYHQ==
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:
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
regenerate "^1.4.0"
regenerate-unicode-properties "^8.0.2"
regjsgen "^0.5.0"
regjsparser "^0.6.0"
unicode-match-property-ecmascript "^1.0.4"
unicode-match-property-value-ecmascript "^1.1.0"
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
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
regjsgen@^0.5.0:
version "0.5.0"
resolved "https://registry.yarnpkg.com/regjsgen/-/regjsgen-0.5.0.tgz#a7634dc08f89209c2049adda3525711fb97265dd"
integrity sha512-RnIrLhrXCX5ow/E5/Mh2O4e/oa1/jW0eaBKTSy3LaCj+M3Bqvm97GWDp2yUtzIs4LEn65zR2yiYGFqb2ApnzDA==
regjsparser@^0.6.0:
version "0.6.0"
resolved "https://registry.yarnpkg.com/regjsparser/-/regjsparser-0.6.0.tgz#f1e6ae8b7da2bae96c99399b868cd6c933a2ba9c"
integrity sha512-RQ7YyokLiQBomUJuUG8iGVvkgOLxwyZM8k6d3q5SAXpg4r5TZJZigKFvC6PpD+qQ98bCDC5YelPeA3EucDoNeQ==
dependencies:
jsesc "~0.5.0"
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
remark-parse@^5.0.0:
version "5.0.0"
resolved "https://registry.yarnpkg.com/remark-parse/-/remark-parse-5.0.0.tgz#4c077f9e499044d1d5c13f80d7a98cf7b9285d95"
integrity sha512-b3iXszZLH1TLoyUzrATcTQUZrwNl1rE70rVdSruJFlDaJ9z5aMkhrG43Pp68OgfHndL/ADz6V69Zow8cTQu+JA==
dependencies:
collapse-white-space "^1.0.2"
is-alphabetical "^1.0.0"
is-decimal "^1.0.0"
is-whitespace-character "^1.0.0"
is-word-character "^1.0.0"
markdown-escapes "^1.0.0"
parse-entities "^1.1.0"
repeat-string "^1.5.4"
state-toggle "^1.0.0"
trim "0.0.1"
trim-trailing-lines "^1.0.0"
unherit "^1.0.4"
unist-util-remove-position "^1.0.0"
vfile-location "^2.0.0"
xtend "^4.0.1"
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:
version "0.3.0"
resolved "https://registry.yarnpkg.com/remove-markdown/-/remove-markdown-0.3.0.tgz#5e4b667493a93579728f3d52ecc1db9ca505dc98"
integrity sha1-XktmdJOpNXlyjz1S7MHbnKUF3Jg=
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
remove-trailing-separator@^1.0.1:
version "1.1.0"
resolved "https://registry.yarnpkg.com/remove-trailing-separator/-/remove-trailing-separator-1.1.0.tgz#c24bce2a283adad5bc3f58e0d48249b92379d8ef"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-wkvOKig62tW8P1jg1IJJuSN52O8=
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
repeat-element@^1.1.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.3"
resolved "https://registry.yarnpkg.com/repeat-element/-/repeat-element-1.1.3.tgz#782e0d825c0c5a3bb39731f84efee6b742e6b1ce"
integrity sha512-ahGq0ZnV5m5XtZLMb+vP76kcAM5nkLqk0lpqAuojSKGgQtn4eRi4ZZGm2olo2zKFH+sMsWaqOCW1dqAnOru72g==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
repeat-string@^1.5.4, repeat-string@^1.6.1:
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
version "1.6.1"
resolved "https://registry.yarnpkg.com/repeat-string/-/repeat-string-1.6.1.tgz#8dcae470e1c88abc2d600fff4a776286da75e637"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-jcrkcOHIirwtYA//Sndihtp15jc=
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
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
replace-ext@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/replace-ext/-/replace-ext-1.0.0.tgz#de63128373fcbf7c3ccfa4de5a480c45a67958eb"
integrity sha1-3mMSg3P8v3w8z6TeWkgMRaZ5WOs=
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
request-promise-core@1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/request-promise-core/-/request-promise-core-1.1.2.tgz#339f6aababcafdb31c799ff158700336301d3346"
integrity sha512-UHYyq1MO8GsefGEt7EprS8UrXsm1TxEvFUX1IMTuSLU2Rh7fTIdFtl8xD7JiEYiWU2dl+NYAjCTksTehQUxPag==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
lodash "^4.17.11"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
request-promise-native@^1.0.5:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.7"
resolved "https://registry.yarnpkg.com/request-promise-native/-/request-promise-native-1.0.7.tgz#a49868a624bdea5069f1251d0a836e0d89aa2c59"
integrity sha512-rIMnbBdgNViL37nZ1b3L/VfPOpSi0TqVDQPAvO6U14lMzOLrt5nilxCQqtDKhZeDiW0/hkCXGoQjhgJd/tCh6w==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
request-promise-core "1.1.2"
stealthy-require "^1.1.1"
tough-cookie "^2.3.3"
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
request@^2.87.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.88.0"
resolved "https://registry.yarnpkg.com/request/-/request-2.88.0.tgz#9c2fca4f7d35b592efe57c7f0a55e81052124fef"
integrity sha512-NAqBSrijGLZdM0WZNsInLJpkJokL72XYjUpnB0iwsRgxh7dB6COrHnTBNwN0E+lHDAJzu7kLAkDeY08z2/A0hg==
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:
aws-sign2 "~0.7.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
aws4 "^1.8.0"
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
caseless "~0.12.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
combined-stream "~1.0.6"
extend "~3.0.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
forever-agent "~0.6.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
form-data "~2.3.2"
har-validator "~5.1.0"
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
http-signature "~1.2.0"
is-typedarray "~1.0.0"
isstream "~0.1.2"
json-stringify-safe "~5.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
mime-types "~2.1.19"
oauth-sign "~0.9.0"
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
performance-now "^2.1.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
qs "~6.5.2"
safe-buffer "^5.1.2"
tough-cookie "~2.4.3"
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
tunnel-agent "^0.6.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
uuid "^3.3.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
require-directory@^2.1.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/require-directory/-/require-directory-2.1.1.tgz#8c64ad5fd30dab1c976e2344ffe7f792a6a6df42"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-jGStX9MNqxyXbiNE/+f3kqam30I=
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
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
"require-like@>= 0.1.1":
version "0.1.2"
resolved "https://registry.yarnpkg.com/require-like/-/require-like-0.1.2.tgz#ad6f30c13becd797010c468afa775c0c0a6b47fa"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-rW8wwTvs15cBDEaK+ndcDAprR/o=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +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
require-main-filename@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/require-main-filename/-/require-main-filename-1.0.1.tgz#97f717b69d48784f5f526a6c5aa8ffdda055a4d1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-l/cXtp1IeE9fUmpsWqj/3aBVpNE=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
require-main-filename@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/require-main-filename/-/require-main-filename-2.0.0.tgz#d0b329ecc7cc0f61649f62215be69af54aa8989b"
integrity sha512-NKN5kMDylKuldxYLSUfrbo5Tuzh4hd+2E8NPPX02mZtn1VuREQToYe/ZdlJy+J3uCpfaiGF05e7B8W0iXbQHmg==
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
requires-port@^1.0.0:
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
version "1.0.0"
resolved "https://registry.yarnpkg.com/requires-port/-/requires-port-1.0.0.tgz#925d2601d39ac485e091cf0da5c6e694dc3dcaff"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-kl0mAdOaxIXgkc8NpcbmlNw9yv8=
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
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
resize-observer-polyfill@^1.5.0:
version "1.5.1"
resolved "https://registry.yarnpkg.com/resize-observer-polyfill/-/resize-observer-polyfill-1.5.1.tgz#0e9020dd3d21024458d4ebd27e23e40269810464"
integrity sha512-LwZrotdHOo12nQuZlHEmtuXdqGoOD0OhaxopaNFxWzInpEgaLWoVuAMbTzixuosCx2nEG58ngzW3vxdWoxIgdg==
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
resolve-cwd@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/resolve-cwd/-/resolve-cwd-2.0.0.tgz#00a9f7387556e27038eae232caa372a6a59b665a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-AKn3OHVW4nA46uIyyqNypqWbZlo=
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:
resolve-from "^3.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
resolve-dir@^1.0.0, resolve-dir@^1.0.1:
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
version "1.0.1"
resolved "https://registry.yarnpkg.com/resolve-dir/-/resolve-dir-1.0.1.tgz#79a40644c362be82f26effe739c9bb5382046f43"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-eaQGRMNivoLybv/nOcm7U4IEb0M=
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:
expand-tilde "^2.0.0"
global-modules "^1.0.0"
resolve-from@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/resolve-from/-/resolve-from-3.0.0.tgz#b22c7af7d9d6881bc8b6e653335eebcb0a188748"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-six699nWiBvItuZTM17rywoYh0g=
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
resolve-from@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/resolve-from/-/resolve-from-4.0.0.tgz#4abcd852ad32dd7baabfe9b40e00a36db5f392e6"
integrity sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
resolve-url@^0.2.1:
version "0.2.1"
resolved "https://registry.yarnpkg.com/resolve-url/-/resolve-url-0.2.1.tgz#2c637fe77c893afd2a663fe21aa9080068e2052a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-LGN/53yJOv0qZj/iGqkIAGjiBSo=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
resolve@1.1.7:
version "1.1.7"
resolved "https://registry.yarnpkg.com/resolve/-/resolve-1.1.7.tgz#203114d82ad2c5ed9e8e0411b3932875e889e97b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-IDEU2CrSxe2ejgQRs5ModeiJ6Xs=
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
resolve@^1.10.0, resolve@^1.10.1, resolve@^1.11.0, resolve@^1.3.2, resolve@^1.5.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "1.11.1"
resolved "https://registry.yarnpkg.com/resolve/-/resolve-1.11.1.tgz#ea10d8110376982fef578df8fc30b9ac30a07a3e"
integrity sha512-vIpgF6wfuJOZI7KKKSP+HmiKggadPQAdsp5HiC1mvqnfp0gF1vdwgBWZIdrVft9pgqoMFQN+R7BSWZiBxx+BBw==
dependencies:
path-parse "^1.0.6"
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
restore-cursor@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/restore-cursor/-/restore-cursor-2.0.0.tgz#9f7ee287f82fd326d4fd162923d62129eee0dfaf"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-n37ih/gv0ybU/RYpI9YhKe7g368=
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:
onetime "^2.0.0"
signal-exit "^3.0.2"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
ret@~0.1.10:
version "0.1.15"
resolved "https://registry.yarnpkg.com/ret/-/ret-0.1.15.tgz#b8a4825d5bdb1fc3f6f53c2bc33f81388681c7bc"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-TTlYpa+OL+vMMNG24xSlQGEJ3B/RzEfUlLct7b5G/ytav+wPrplCpVMFuwzXbkecJrb6IYo1iFb0S9v37754mg==
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
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:
version "0.12.0"
resolved "https://registry.yarnpkg.com/retry/-/retry-0.12.0.tgz#1b42a6266a21f07421d1b0b54b7dc167b01c013b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-G0KmJmoh8HQh0bC1S33BZ7AcATs=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
rimraf@2.6.3, rimraf@^2.5.4, rimraf@^2.6.1, rimraf@^2.6.3:
Add CLI command to clear sourcecred data directory (#1111) Resolves #1067 Adds the CLI commands: `sourcecred clear --all` -- removes the $SOURCECRED_DIRECTORY `sourcecred clear --cache` -- removes the cache directory `sourcecred clear --help` -- provides usage info `sourcecred clear` -- prompts the user to be more specific Test plan: The unit tests ensure that the command is properly wired into the sourcecred CLI, including help text integration. However, just to be safe, we can start by verifying that calling `sourcecred` without arguments lists the `clear` command as a valid option, and that calling `sourcecred help clear` prints help information. (Note: it's necessary to run `yarn backend` before testing these changes) The unit tests also ensure that the command removes the proper directories, so there isn't really a need to manually test it, although the reviewer may choose to do so to be safe. Although out of scope for unit tests on this function, we can also do integration tests, to make sure that running the clear command doesn't leave the sourcecred directory in an invalid state from the perspective of the `load` command. ```js $ yarn backend; $ node bin/sourcecred.js load sourcecred/example-github; $ node bin/sourcecred.js clear --cache; $ node bin/sourcecred.js load sourcecred/example-github; $ node bin/sourcecred.js clear --all; $ node bin/sourcecred.js load sourcecred/example-github; ``` The expected behavior of the above command block is that the load command never fails or throws an error. @decentralion and I discussed the scenario where `rimraf` errors. We decided that testing this scenario wasn't necessary, because `rimraf` doesn't error if a directory doesn't exist, and rimraf's maintainer suggests [monkey-patching the fs module] to get rimraf to error in testing scenarios. Thanks @decentralion for reviewing and pair-programming this with me. [monkey-patching the fs module]: https://github.com/isaacs/rimraf/issues/31#issuecomment-29534796
2019-05-13 09:59:58 +00:00
version "2.6.3"
resolved "https://registry.yarnpkg.com/rimraf/-/rimraf-2.6.3.tgz#b2d104fe0d8fb27cf9e0a1cda8262dd3833c6cab"
integrity sha512-mwqeW5XsA2qAejG46gYdENaxXjx9onRNCfn7L0duuP4hCuTIi/QO7PDK07KJfp1d+izWPrzEJDcSqBa0OZQriA==
dependencies:
glob "^7.1.3"
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
ripemd160@^2.0.0, ripemd160@^2.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.0.2"
resolved "https://registry.yarnpkg.com/ripemd160/-/ripemd160-2.0.2.tgz#a1c1a6f624751577ba5d07914cbc92850585890c"
integrity sha512-ii4iagi25WusVoiC4B4lq7pbXfAp3D9v5CwfkY33vffw2+pkDjY1D8GaN7spsxvCSx8dkPqOZCEZyfxcmJG2IA==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
hash-base "^3.0.0"
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
inherits "^2.0.1"
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
rst-selector-parser@^2.2.3:
version "2.2.3"
resolved "https://registry.yarnpkg.com/rst-selector-parser/-/rst-selector-parser-2.2.3.tgz#81b230ea2fcc6066c89e3472de794285d9b03d91"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-gbIw6i/MYGbInjRy3nlChdmwPZE=
Use Enzyme to test ContributionList dynamics (#102) Summary: This is our first dynamic test of a React component! Enzyme looks pretty easy to use to me, for both snapshot tests and interaction simulation. In doing so, we catch a minor bug in the edge case where a contribution is not owned by any plugin (`colSpan`, not `colspan`). This edge case does not appear in the sample data, but it does appear in the test data, even prior to this commit. The previous renderer, `react-test-renderer`, appears not to surface this error. Furthermore, this bug did not cause any user-visible errors except a `console.error`. Test Plan: Inspect the snapshot file to make sure that it is reasonable. (The existing test case has its snapshot regenerated due to formatting differences between the two renderers.) To test that the browser error is fixed, render a contribution list on a GitHub graph but with an empty adapter set. One way to do this is to comment out line 7 of `standardAdapterSet.js`; alternately, you can use the React Dev Tools to select the `ContributionList` node, then run ```js $r.props.adapters.adapters = {}; $r.forceUpdate(); ``` Note subsequently that there is no console error and that the `<td>`s in question span three columns. wchargin-branch: contributionlist-dynamic-test
2018-03-22 00:35:17 +00:00
dependencies:
lodash.flattendeep "^4.4.0"
nearley "^2.7.10"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
rsvp@^4.8.4:
version "4.8.5"
resolved "https://registry.yarnpkg.com/rsvp/-/rsvp-4.8.5.tgz#c8f155311d167f68f21e168df71ec5b083113734"
integrity sha512-nfMOlASu9OnRJo1mbEk2cz0D56a1MBNrJ7orjRZQG10XDyuvwksKbuXNp6qa+kbn839HwjwhBzhFmdsaEAfauA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
run-async@^2.2.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/run-async/-/run-async-2.3.0.tgz#0371ab4ae0bdd720d4166d7dfda64ff7a445a6c0"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-A3GrSuC91yDUFm19/aZP96RFpsA=
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:
is-promise "^2.1.0"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
run-queue@^1.0.0, run-queue@^1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/run-queue/-/run-queue-1.0.3.tgz#e848396f057d223f24386924618e25694161ec47"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-6Eg5bwV9Ij8kOGkkYY4laUFh7Ec=
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
aproba "^1.1.1"
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
rx-lite-aggregates@^4.0.8:
version "4.0.8"
resolved "https://registry.yarnpkg.com/rx-lite-aggregates/-/rx-lite-aggregates-4.0.8.tgz#753b87a89a11c95467c4ac1626c4efc4e05c67be"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-dTuHqJoRyVRnxKwWJsTvxOBcZ74=
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:
rx-lite "*"
rx-lite@*, rx-lite@^4.0.8:
version "4.0.8"
resolved "https://registry.yarnpkg.com/rx-lite/-/rx-lite-4.0.8.tgz#0b1e11af8bc44836f04a6407e92da42467b79444"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Cx4Rr4vESDbwSmQH6S2kJGe3lEQ=
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
Port skeleton of Odyssey frontend (#1132) This commit integrates an bare skeleton of the odyssey frontend that we implemented in the [odyssey-hackathon] repository. You can see the working frontend that we are trying to port over at [sourcecred.io/odyssey-hackathon/][scio]. The prototype in the other repository has some tooling choices which are incompatible/redundant with decisions in our codebase (sass vs aphrodite), and requires some tools not yet present here (svg-react-loader). This commit includes the build and integration work needed to port the prototype frontend into mainline SourceCred. The frontend scaffold isn't yet integrated with any "real" Odyssey data. One potential issue: right now, every page that is rendered from the SourceCred homepage is contained within a [homepage/Page], meaning that it has full SourceCred website styling, along with the SourceCred website header. The [application][scio] also has a header. Currently, I work around this by having the Odyssey UI cover up the base header (via absolute positioning), which works but is hacky. We can consider more principled solutions: - Finding a way to specify routes which aren't contained by [homepage/Page]; maybe by adding a new top-level route [here][route-alternative]. - Unify the headers for the Odyssey viewer and the page as a whole (sounds like inappropriate entanglement?) - Have a website header and also an application header (sounds ugly?) [homepage/Page]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/Page.js [route-alternative]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/createRoutes.js#L17 Test plan: Run `yarn start`, and then navigate to `localhost:8080/odyssey/`. observe that a working website is displayed, and that the cred logo next to the word "SourceCred" is loaded properly (i.e. svg-react-loader is integrated properly). Observe that there are no build/compile errors from either `yarn start` or `yarn build`. Also, observe that the UI looks passably nice, and that if the number of elements in the entity lists is larger than can be displayed, the sidebar pane scrolls independently. The UI was tested in both Chrome and Firefox. [odyssey-hackathon]: https://github.com/sourcecred/odyssey-hackathon [scio]: https://sourcecred.io/odyssey-hackathon/ Thanks to @jmnemo, as the implementation is based on [his work]. [his work]: https://github.com/jmnemo/hackathon-event/
2019-05-06 15:15:39 +00:00
rx@4.1.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/rx/-/rx-4.1.0.tgz#a5f13ff79ef3b740fe30aa803fb09f98805d4782"
integrity sha1-pfE/957zt0D+MKqAP7CfmIBdR4I=
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
rxjs@^6.4.0:
version "6.5.2"
resolved "https://registry.yarnpkg.com/rxjs/-/rxjs-6.5.2.tgz#2e35ce815cd46d84d02a209fb4e5921e051dbec7"
integrity sha512-HUb7j3kvb7p7eCUHE3FqjoDsC1xfZQ4AHFWfTKSpZ+sAhhz5X1WX0ZuUqWbzB2QhSLp3DoLUG+hMdEDKqWo2Zg==
dependencies:
tslib "^1.9.0"
Regenerate yarn.lock file (#1204) I've regenerated the yarn.lock file (by removing it and then re-running yarn). This picks up [a fix I authored][fix] for node-eval, which was preventing `yarn test --full` from passing in node 10 and 12. With this upgrde of transitive dependencies, we're now ready to officially support newer versions of node. Test plan: `yarn test` passes.
2019-07-06 14:02:04 +00:00
safe-buffer@5.1.2, safe-buffer@~5.1.0, safe-buffer@~5.1.1:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
version "5.1.2"
resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.1.2.tgz#991ec69d296e0313747d59bdfd2b745c35f8828d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Regenerate yarn.lock file (#1204) I've regenerated the yarn.lock file (by removing it and then re-running yarn). This picks up [a fix I authored][fix] for node-eval, which was preventing `yarn test --full` from passing in node 10 and 12. With this upgrde of transitive dependencies, we're now ready to officially support newer versions of node. Test plan: `yarn test` passes.
2019-07-06 14:02:04 +00:00
safe-buffer@>=5.1.0, safe-buffer@^5.0.1, safe-buffer@^5.1.0, safe-buffer@^5.1.1, safe-buffer@^5.1.2:
version "5.2.0"
resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.2.0.tgz#b74daec49b1148f88c64b68d49b1e815c1f2f519"
integrity sha512-fZEwUGbVl7kouZs1jCdMLdt95hdIv0ZeHg6L7qPeciMZhZ+/gdesW4wgTARkrFWEpspjEATAzUGPG8N2jJiwbg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
safe-regex@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/safe-regex/-/safe-regex-1.1.0.tgz#40a3669f3b077d1e943d44629e157dd48023bf2e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-QKNmnzsHfR6UPURinhV91IAjvy4=
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:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
ret "~0.1.10"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
"safer-buffer@>= 2.1.2 < 3", safer-buffer@^2.0.2, safer-buffer@^2.1.0, safer-buffer@~2.1.0:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
version "2.1.2"
resolved "https://registry.yarnpkg.com/safer-buffer/-/safer-buffer-2.1.2.tgz#44fa161b0187b9549dd84bb91802f9bd8385cd6a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
sane@^4.0.3:
version "4.1.0"
resolved "https://registry.yarnpkg.com/sane/-/sane-4.1.0.tgz#ed881fd922733a6c461bc189dc2b6c006f3ffded"
integrity sha512-hhbzAgTIX8O7SHfp2c8/kREfEn4qO/9q8C9beyY6+tvZ87EpoZ3i1RIEvp27YBswnNbY9mWd6paKVmKbAgLfZA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"@cnakazawa/watch" "^1.0.3"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
anymatch "^2.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
capture-exit "^2.0.0"
exec-sh "^0.3.2"
execa "^1.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
fb-watchman "^2.0.0"
micromatch "^3.1.4"
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
minimist "^1.1.1"
walker "~1.0.5"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
sax@>=0.6.0, sax@^1.2.4:
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
version "1.2.4"
resolved "https://registry.yarnpkg.com/sax/-/sax-1.2.4.tgz#2816234e2378bddc4e5354fab5caa895df7100d9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
scheduler@^0.13.6:
version "0.13.6"
resolved "https://registry.yarnpkg.com/scheduler/-/scheduler-0.13.6.tgz#466a4ec332467b31a91b9bf74e5347072e4cd889"
integrity sha512-IWnObHt413ucAYKsD9J1QShUKkbKLQQHdxRyw73sw4FN26iWr3DY/H34xGPe4nmL1DwXyWmSWmMrA9TfQbE/XQ==
dependencies:
loose-envify "^1.1.0"
object-assign "^4.1.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
schema-utils@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/schema-utils/-/schema-utils-1.0.0.tgz#0b79a93204d7b600d4b2850d1f66c2a34951c770"
integrity sha512-i27Mic4KovM/lnGsy8whRCHhc7VicJajAjTrYg11K9zfZXnYIt4k5F+kZkwjnrhKzLic/HLU4j11mjsz2G/75g==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
ajv "^6.1.0"
ajv-errors "^1.0.0"
ajv-keywords "^3.1.0"
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
select-hose@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/select-hose/-/select-hose-2.0.0.tgz#625d8658f865af43ec962bfc376a37359a4994ca"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-Yl2GWPhlr0Psliv8N2o3NZpJlMo=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
selfsigned@^1.10.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.10.4"
resolved "https://registry.yarnpkg.com/selfsigned/-/selfsigned-1.10.4.tgz#cdd7eccfca4ed7635d47a08bf2d5d3074092e2cd"
integrity sha512-9AukTiDmHXGXWtWjembZ5NDmVvP2695EtpgbCsxCa68w3c88B+alqbmZ4O3hZ4VWGXeGWzEVdvqgAJD8DQPCDw==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
node-forge "0.7.5"
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
"semver@2 || 3 || 4 || 5", semver@^5.3.0, semver@^5.4.1, semver@^5.5.0, semver@^5.5.1, semver@^5.6.0, semver@^5.7.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "5.7.0"
resolved "https://registry.yarnpkg.com/semver/-/semver-5.7.0.tgz#790a7cf6fea5459bac96110b29b60412dc8ff96b"
integrity sha512-Ya52jSX2u7QKghxeoFGpLwCtGlt7j0oY9DYb5apt9nPlJ42ID+ulTXESnt/qAQcoSERyZ5sl3LDIOw0nAn/5DA==
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
semver@^6.0.0, semver@^6.1.1:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "6.2.0"
resolved "https://registry.yarnpkg.com/semver/-/semver-6.2.0.tgz#4d813d9590aaf8a9192693d6c85b9344de5901db"
integrity sha512-jdFC1VdUGT/2Scgbimf7FSx9iJLXoqfglSF+gJeuNWVpiE37OIbc1jywR/GJyFdz3mnkz2/id0L0J/cr0izR5A==
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
send@0.17.1:
version "0.17.1"
resolved "https://registry.yarnpkg.com/send/-/send-0.17.1.tgz#c1d8b059f7900f7466dd4938bdc44e11ddb376c8"
integrity sha512-BsVKsiGcQMFwT8UxypobUKyv7irCNRHk1T0G680vk88yf6LBByGcZJOTJCrTP2xVN6yI+XjPJcNuE3V4fT9sAg==
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
dependencies:
debug "2.6.9"
depd "~1.1.2"
destroy "~1.0.4"
encodeurl "~1.0.2"
escape-html "~1.0.3"
etag "~1.8.1"
fresh "0.5.2"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
http-errors "~1.7.2"
mime "1.6.0"
ms "2.1.1"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
on-finished "~2.3.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
range-parser "~1.2.1"
statuses "~1.5.0"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
serialize-javascript@^1.7.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.7.0"
resolved "https://registry.yarnpkg.com/serialize-javascript/-/serialize-javascript-1.7.0.tgz#d6e0dfb2a3832a8c94468e6eb1db97e55a192a65"
integrity sha512-ke8UG8ulpFOxO8f8gRYabHQe/ZntKlcig2Mp+8+URDP1D8vJZ0KUt7LYo07q25Z/+JVSgpr/cui9PIp5H6/+nA==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
serve-index@^1.9.1:
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
version "1.9.1"
resolved "https://registry.yarnpkg.com/serve-index/-/serve-index-1.9.1.tgz#d3768d69b1e7d82e5ce050fff5b453bea12a9239"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-03aNabHn2C5c4FD/9bRTvqEqkjk=
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:
accepts "~1.3.4"
batch "0.6.1"
debug "2.6.9"
escape-html "~1.0.3"
http-errors "~1.6.2"
mime-types "~2.1.17"
parseurl "~1.3.2"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
serve-static@1.14.1:
version "1.14.1"
resolved "https://registry.yarnpkg.com/serve-static/-/serve-static-1.14.1.tgz#666e636dc4f010f7ef29970a88a674320898b2f9"
integrity sha512-JMrvUwE54emCYWlTI+hGrGv5I8dEwmco/00EvkzIIsR7MqrHonbD9pO2MOfFnpFntl7ecpZs+3mW+XbQZu9QCg==
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +00:00
dependencies:
encodeurl "~1.0.2"
escape-html "~1.0.3"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
parseurl "~1.3.3"
send "0.17.1"
Add dependency on express (#233) wchargin-branch: express
2018-05-08 03:05:52 +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
set-blocking@^2.0.0, set-blocking@~2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/set-blocking/-/set-blocking-2.0.0.tgz#045f9782d011ae9a6803ddd382b24392b3d890f7"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-BF+XgtARrppoA93TgrJDkrPYkPc=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
set-value@^2.0.0, set-value@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/set-value/-/set-value-2.0.1.tgz#a18d40530e6f07de4228c7defe4227af8cad005b"
integrity sha512-JxHc1weCN68wRY0fhCoXpyK55m/XPHafOmK4UWD7m2CI14GMcFypt4w/0+NV5f/ZMby2F6S2wwA7fgynh9gWSw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
extend-shallow "^2.0.1"
is-extendable "^0.1.1"
is-plain-object "^2.0.3"
split-string "^3.0.1"
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
setimmediate@^1.0.4, setimmediate@^1.0.5:
version "1.0.5"
resolved "https://registry.yarnpkg.com/setimmediate/-/setimmediate-1.0.5.tgz#290cbb232e306942d7d7ea9b83732ab7856f8285"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-KQy7Iy4waULX1+qbg3Mqt4VvgoU=
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
setprototypeof@1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/setprototypeof/-/setprototypeof-1.1.0.tgz#d0bd85536887b6fe7c0d818cb962d9d91c54e656"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-BvE/TwpZX4FXExxOxZyRGQQv651MSwmWKZGqvmPcRIjDqWub67kTKuIMx43cZZrS/cBBzwBcNDWoFxt2XEFIpQ==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
setprototypeof@1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/setprototypeof/-/setprototypeof-1.1.1.tgz#7e95acb24aa92f5885e0abef5ba131330d4ae683"
integrity sha512-JvdAWfbXeIGaZ9cILp38HntZSFSo3mWg6xGcJJsd+d4aRMOqauag1C63dJfDw7OaMYwEbHMOxEZ1lqVRYP2OAw==
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
sha.js@^2.4.0, sha.js@^2.4.8:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.4.11"
resolved "https://registry.yarnpkg.com/sha.js/-/sha.js-2.4.11.tgz#37a5cf0b81ecbc6943de109ba2960d1b26584ae7"
integrity sha512-QMEp5B7cftE7APOjk5Y6xgrbWu+WkLVQwk8JNjZ8nKRciZaByEW6MubieAiToS7+dwvrjGhH8jRXz3MVd0AYqQ==
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:
inherits "^2.0.1"
safe-buffer "^5.0.1"
shebang-command@^1.2.0:
version "1.2.0"
resolved "https://registry.yarnpkg.com/shebang-command/-/shebang-command-1.2.0.tgz#44aac65b695b03398968c39f363fee5deafdf1ea"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-RKrGW2lbAzmJaMOfNj/uXer98eo=
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:
shebang-regex "^1.0.0"
shebang-regex@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/shebang-regex/-/shebang-regex-1.0.0.tgz#da42f49740c0b42db2ca9728571cb190c98efea3"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-2kL0l0DAtC2yypcoVxyxkMmO/qM=
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
shell-quote@1.6.1:
version "1.6.1"
resolved "https://registry.yarnpkg.com/shell-quote/-/shell-quote-1.6.1.tgz#f4781949cce402697127430ea3b3c5476f481767"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-9HgZSczkAmlxJ0MOo7PFR29IF2c=
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:
array-filter "~0.0.0"
array-map "~0.0.0"
array-reduce "~0.0.0"
jsonify "~0.0.0"
shellwords@^0.1.1:
version "0.1.1"
resolved "https://registry.yarnpkg.com/shellwords/-/shellwords-0.1.1.tgz#d6b9181c1a48d397324c84871efbcfc73fc0654b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-vFwSUfQvqybiICwZY5+DAWIPLKsWO31Q91JSKl3UYv+K5c2QRPzn0qzec6QPu1Qc9eHYItiP3NdJqNVqetYAww==
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
signal-exit@^3.0.0, signal-exit@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/signal-exit/-/signal-exit-3.0.2.tgz#b5fdc08f1287ea1178628e415e25132b73646c6d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-tf3AjxKH6hF4Yo5BXiUTK3NkbG0=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
sisteransi@^1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/sisteransi/-/sisteransi-1.0.2.tgz#ec57d64b6f25c4f26c0e2c7dd23f2d7f12f7e418"
integrity sha512-ZcYcZcT69nSLAR2oLN2JwNmLkJEKGooFMCdvOkFrToUt/WfcRWqhIg4P4KwY4dmLbuyXIx4o4YmPsvMRJYJd/w==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
slash@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/slash/-/slash-1.0.0.tgz#c41f2f6c39fc16d1cd17ad4b5d896114ae470d55"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-xB8vbDn8FtHNF61LXYlhFK5HDVU=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
slash@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/slash/-/slash-2.0.0.tgz#de552851a1759df3a8f206535442f5ec4ddeab44"
integrity sha512-ZYKh3Wh2z1PpEXWr0MpSBZ0V6mZHAQfYevttO11c51CaWjGTaadiKZ+wVt1PbMlDV5qhMFslpZCemhwOK7C89A==
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
slice-ansi@^2.1.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/slice-ansi/-/slice-ansi-2.1.0.tgz#cacd7693461a637a5788d92a7dd4fba068e81636"
integrity sha512-Qu+VC3EwYLldKa1fCxuuvULvSJOKEgk9pi8dZeCVK7TqBfUNTH4sFkk4joj8afVSfAYgJoSOetjx9QWOJ5mYoQ==
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:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
ansi-styles "^3.2.0"
astral-regex "^1.0.0"
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
is-fullwidth-code-point "^2.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
snapdragon-node@^2.0.1:
version "2.1.1"
resolved "https://registry.yarnpkg.com/snapdragon-node/-/snapdragon-node-2.1.1.tgz#6c175f86ff14bdb0724563e8f3c1b021a286853b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-O27l4xaMYt/RSQ5TR3vpWCAB5Kb/czIcqUFOM/C4fYcLnbZUc1PkjTAMjof2pBWaSTwOUd6qUHcFGVGj7aIwnw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
define-property "^1.0.0"
isobject "^3.0.0"
snapdragon-util "^3.0.1"
snapdragon-util@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/snapdragon-util/-/snapdragon-util-3.0.1.tgz#f956479486f2acd79700693f6f7b805e45ab56e2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-mbKkMdQKsjX4BAL4bRYTj21edOf8cN7XHdYUJEe+Zn99hVEYcMvKPct1IqNe7+AZPirn8BCDOQBHQZknqmKlZQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
kind-of "^3.2.0"
snapdragon@^0.8.1:
version "0.8.2"
resolved "https://registry.yarnpkg.com/snapdragon/-/snapdragon-0.8.2.tgz#64922e7c565b0e14204ba1aa7d6964278d25182d"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-FtyOnWN/wCHTVXOMwvSv26d+ko5vWlIDD6zoUJ7LW8vh+ZBC8QdljveRP+crNrtBwioEUWy/4dMtbBjA4ioNlg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
base "^0.11.1"
debug "^2.2.0"
define-property "^0.2.5"
extend-shallow "^2.0.1"
map-cache "^0.2.2"
source-map "^0.5.6"
source-map-resolve "^0.5.0"
use "^3.1.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
sockjs-client@1.1.5:
version "1.1.5"
resolved "https://registry.yarnpkg.com/sockjs-client/-/sockjs-client-1.1.5.tgz#1bb7c0f7222c40f42adf14f4442cbd1269771a83"
integrity sha1-G7fA9yIsQPQq3xT0RCy9Eml3GoM=
dependencies:
debug "^2.6.6"
eventsource "0.1.6"
faye-websocket "~0.11.0"
inherits "^2.0.1"
json3 "^3.3.2"
url-parse "^1.1.8"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
sockjs-client@1.3.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/sockjs-client/-/sockjs-client-1.3.0.tgz#12fc9d6cb663da5739d3dc5fb6e8687da95cb177"
integrity sha512-R9jxEzhnnrdxLCNln0xg5uGHqMnkhPSTzUZH2eXcR03S/On9Yvoq2wyUZILRUhZCNVu2PmwWVoyuiPz8th8zbg==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
debug "^3.2.5"
eventsource "^1.0.7"
faye-websocket "~0.11.1"
inherits "^2.0.3"
json3 "^3.3.2"
url-parse "^1.4.3"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
sockjs@0.3.19:
version "0.3.19"
resolved "https://registry.yarnpkg.com/sockjs/-/sockjs-0.3.19.tgz#d976bbe800af7bd20ae08598d582393508993c0d"
integrity sha512-V48klKZl8T6MzatbLlzzRNhMepEys9Y4oGFpypBFFn1gLI/QQ9HtLLyWJNbPlwGLelOVOEijUbTTJeLLI59jLw==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
faye-websocket "^0.10.0"
uuid "^3.0.1"
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
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
source-list-map@^1.1.1:
version "1.1.2"
resolved "https://registry.yarnpkg.com/source-list-map/-/source-list-map-1.1.2.tgz#9889019d1024cce55cdc069498337ef6186a11a1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-mIkBnRAkzOVc3AaUmDN+9hhqEaE=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +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
source-list-map@^2.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.0.1"
resolved "https://registry.yarnpkg.com/source-list-map/-/source-list-map-2.0.1.tgz#3993bd873bfc48479cca9ea3a547835c7c154b34"
integrity sha512-qnQ7gVMxGNxsiL4lEuJwe/To8UnK7fAnmbGEEH8RpLouuKbeEm0lhbQVFIrNSuB+G7tVrAlVsZgETT5nljf+Iw==
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
Port skeleton of Odyssey frontend (#1132) This commit integrates an bare skeleton of the odyssey frontend that we implemented in the [odyssey-hackathon] repository. You can see the working frontend that we are trying to port over at [sourcecred.io/odyssey-hackathon/][scio]. The prototype in the other repository has some tooling choices which are incompatible/redundant with decisions in our codebase (sass vs aphrodite), and requires some tools not yet present here (svg-react-loader). This commit includes the build and integration work needed to port the prototype frontend into mainline SourceCred. The frontend scaffold isn't yet integrated with any "real" Odyssey data. One potential issue: right now, every page that is rendered from the SourceCred homepage is contained within a [homepage/Page], meaning that it has full SourceCred website styling, along with the SourceCred website header. The [application][scio] also has a header. Currently, I work around this by having the Odyssey UI cover up the base header (via absolute positioning), which works but is hacky. We can consider more principled solutions: - Finding a way to specify routes which aren't contained by [homepage/Page]; maybe by adding a new top-level route [here][route-alternative]. - Unify the headers for the Odyssey viewer and the page as a whole (sounds like inappropriate entanglement?) - Have a website header and also an application header (sounds ugly?) [homepage/Page]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/Page.js [route-alternative]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/createRoutes.js#L17 Test plan: Run `yarn start`, and then navigate to `localhost:8080/odyssey/`. observe that a working website is displayed, and that the cred logo next to the word "SourceCred" is loaded properly (i.e. svg-react-loader is integrated properly). Observe that there are no build/compile errors from either `yarn start` or `yarn build`. Also, observe that the UI looks passably nice, and that if the number of elements in the entity lists is larger than can be displayed, the sidebar pane scrolls independently. The UI was tested in both Chrome and Firefox. [odyssey-hackathon]: https://github.com/sourcecred/odyssey-hackathon [scio]: https://sourcecred.io/odyssey-hackathon/ Thanks to @jmnemo, as the implementation is based on [his work]. [his work]: https://github.com/jmnemo/hackathon-event/
2019-05-06 15:15:39 +00:00
source-map-resolve@^0.5.0, source-map-resolve@^0.5.2:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
version "0.5.2"
resolved "https://registry.yarnpkg.com/source-map-resolve/-/source-map-resolve-0.5.2.tgz#72e2cc34095543e43b2c62b2c4c10d4a9054f259"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-MjqsvNwyz1s0k81Goz/9vRBe9SZdB09Bdw+/zYyO+3CuPk6fouTaxscHkgtE8jKvf01kVfl8riHzERQ/kefaSA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
atob "^2.1.1"
decode-uri-component "^0.2.0"
resolve-url "^0.2.1"
source-map-url "^0.4.0"
urix "^0.1.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
source-map-support@^0.5.6, source-map-support@~0.5.12:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "0.5.12"
resolved "https://registry.yarnpkg.com/source-map-support/-/source-map-support-0.5.12.tgz#b4f3b10d51857a5af0138d3ce8003b201613d599"
integrity sha512-4h2Pbvyy15EE02G+JOZpUCmqWJuqrs+sEkzewTm++BPi7Hvn/HwcqLAcNxYAyI0x13CpPPn+kMjl+hplXMHITQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
buffer-from "^1.0.0"
source-map "^0.6.0"
source-map-url@^0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/source-map-url/-/source-map-url-0.4.0.tgz#3e935d7ddd73631b97659956d55128e87b5084a3"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-PpNdfd1zYxuXZZlW1VEo6HtQhKM=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
source-map@^0.5.0, source-map@^0.5.6, source-map@~0.5.3:
deps: remove some unused packages (#789) Summary: Mostly Webpack loaders that have become unused through various config changes. Test Plan: Check that these packages are not used anywhere except as transitive dependencies: ```shell $ git show --format= package.json | > sed '1,4d' | grep '^-' | cut -d\" -f2 | git grep -cf - yarn.lock:3 ``` Also, `yarn && yarn test --full` works, and `yarn start` works, and `yarn backend && node ./bin/sourcecred.js load sourcecred/example-git` works. wchargin-branch: remove-unused-deps
2018-09-06 19:08:45 +00:00
version "0.5.7"
resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.5.7.tgz#8a039d2d1021d22d1ea14c80d8ea468ba2ef3fcc"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-igOdLRAh0i0eoUyA2OpGi6LvP8w=
deps: remove some unused packages (#789) Summary: Mostly Webpack loaders that have become unused through various config changes. Test Plan: Check that these packages are not used anywhere except as transitive dependencies: ```shell $ git show --format= package.json | > sed '1,4d' | grep '^-' | cut -d\" -f2 | git grep -cf - yarn.lock:3 ``` Also, `yarn && yarn test --full` works, and `yarn start` works, and `yarn backend && node ./bin/sourcecred.js load sourcecred/example-git` works. wchargin-branch: remove-unused-deps
2018-09-06 19:08:45 +00:00
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
source-map@^0.6.0, source-map@^0.6.1, source-map@~0.6.1:
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
version "0.6.1"
resolved "https://registry.yarnpkg.com/source-map/-/source-map-0.6.1.tgz#74722af32e9614e9c287a8d0bbde48b5e2f1a263"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
spdx-correct@^3.0.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/spdx-correct/-/spdx-correct-3.1.0.tgz#fb83e504445268f154b074e218c87c003cd31df4"
integrity sha512-lr2EZCctC2BNR7j7WzJ2FpDznxky1sjfxvvYEyzxNyb6lZXHODmEoJeFu4JupYlkfha1KZpJyoqiJ7pgA1qq8Q==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
spdx-expression-parse "^3.0.0"
spdx-license-ids "^3.0.0"
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
spdx-exceptions@^2.1.0:
version "2.2.0"
resolved "https://registry.yarnpkg.com/spdx-exceptions/-/spdx-exceptions-2.2.0.tgz#2ea450aee74f2a89bfb94519c07fcd6f41322977"
integrity sha512-2XQACfElKi9SlVb1CYadKDXvoajPgBVPn/gOQLrTvHdElaVhr7ZEbqJaRnJLVNeaI4cMEAgVCeBMKF6MWRDCRA==
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
spdx-expression-parse@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/spdx-expression-parse/-/spdx-expression-parse-3.0.0.tgz#99e119b7a5da00e05491c9fa338b7904823b41d0"
integrity sha512-Yg6D3XpRD4kkOmTpdgbUiEJFKghJH03fiC1OPll5h/0sO6neh2jqRDVHOQ4o/LMea0tgCkbMgea5ip/e+MkWyg==
dependencies:
spdx-exceptions "^2.1.0"
spdx-license-ids "^3.0.0"
spdx-license-ids@^3.0.0:
version "3.0.4"
resolved "https://registry.yarnpkg.com/spdx-license-ids/-/spdx-license-ids-3.0.4.tgz#75ecd1a88de8c184ef015eafb51b5b48bfd11bb1"
integrity sha512-7j8LYJLeY/Yb6ACbQ7F76qy5jHkp0U6jgBfJsk97bwWlVUnUWsAgpyaCvo17h0/RQGnQ036tVDomiwoI4pDkQA==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
spdy-transport@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/spdy-transport/-/spdy-transport-3.0.0.tgz#00d4863a6400ad75df93361a1608605e5dcdcf31"
integrity sha512-hsLVFE5SjA6TCisWeJXFKniGGOpBgMLmerfO2aCyCU5s7nJ/rpAepqmFifv/GCbSbueEeAJJnmSQ2rKC/g8Fcw==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
debug "^4.1.0"
detect-node "^2.0.4"
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
hpack.js "^2.1.6"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
obuf "^1.1.2"
readable-stream "^3.0.6"
wbuf "^1.7.3"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
spdy@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/spdy/-/spdy-4.0.0.tgz#81f222b5a743a329aa12cea6a390e60e9b613c52"
integrity sha512-ot0oEGT/PGUpzf/6uk4AWLqkq+irlqHXkrdbk51oWONh3bxQmBuljxPNl66zlRRcIJStWq0QkLUCPOPjgjvU0Q==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
debug "^4.1.0"
handle-thing "^2.0.0"
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
http-deceiver "^1.2.7"
select-hose "^2.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
spdy-transport "^3.0.0"
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
split-string@^3.0.1, split-string@^3.0.2:
version "3.1.0"
resolved "https://registry.yarnpkg.com/split-string/-/split-string-3.1.0.tgz#7cb09dda3a86585705c64b39a6466038682e8fe2"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-NzNVhJDYpwceVVii8/Hu6DKfD2G+NrQHlS/V/qgv763EYudVwEcMQNxd2lh+0VrUByXN/oJkl5grOhYWvQUYiw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
extend-shallow "^3.0.0"
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
sprintf-js@~1.0.2:
version "1.0.3"
resolved "https://registry.yarnpkg.com/sprintf-js/-/sprintf-js-1.0.3.tgz#04e6926f662895354f3dd015203633b857297e2c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-BOaSb2YolTVPPdAVIDYzuFcpfiw=
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
sshpk@^1.7.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.16.1"
resolved "https://registry.yarnpkg.com/sshpk/-/sshpk-1.16.1.tgz#fb661c0bef29b39db40769ee39fa70093d6f6877"
integrity sha512-HXXqVUq7+pcKeLqqZj6mHFUMvXtOJt1uoUx09pFW6011inTMxqI8BA8PM95myrIyyKwdnzjdFjLiE6KBPVtJIg==
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:
asn1 "~0.2.3"
assert-plus "^1.0.0"
bcrypt-pbkdf "^1.0.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
dashdash "^1.12.0"
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
ecc-jsbn "~0.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
getpass "^0.1.1"
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
jsbn "~0.1.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
safer-buffer "^2.0.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
tweetnacl "~0.14.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
ssri@^6.0.1:
version "6.0.1"
resolved "https://registry.yarnpkg.com/ssri/-/ssri-6.0.1.tgz#2a3c41b28dd45b62b63676ecb74001265ae9edd8"
integrity sha512-3Wge10hNcT1Kur4PDFwEieXSCMCJs/7WvSACcrMYrNp+b8kDL1/0wJch5Ni2WrtwEa2IO8OsVfeKIciKCDx/QA==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
figgy-pudding "^3.5.1"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
stack-utils@^1.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.2"
resolved "https://registry.yarnpkg.com/stack-utils/-/stack-utils-1.0.2.tgz#33eba3897788558bebfc2db059dc158ec36cebb8"
integrity sha512-MTX+MeG5U994cazkjd/9KNAapsHnibjMLnfXodlkXw76JEea0UiNzrqidzo1emMwk7w5Qhc9jd4Bn9TBb1MFwA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
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
state-toggle@^1.0.0:
version "1.0.2"
resolved "https://registry.yarnpkg.com/state-toggle/-/state-toggle-1.0.2.tgz#75e93a61944116b4959d665c8db2d243631d6ddc"
integrity sha512-8LpelPGR0qQM4PnfLiplOQNJcIN1/r2Gy0xKB2zKnIW2YzPMt2sR4I/+gtPjhN7Svh9kw+zqEg2SFwpBO9iNiw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
static-extend@^0.1.1:
version "0.1.2"
resolved "https://registry.yarnpkg.com/static-extend/-/static-extend-0.1.2.tgz#60809c39cbff55337226fd5e0b520f341f1fb5c6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-YICcOcv/VTNyJv1eC1IPNB8ftcY=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
define-property "^0.2.5"
object-copy "^0.1.0"
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
static-site-generator-webpack-plugin@^3.4.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.4.2"
resolved "https://registry.yarnpkg.com/static-site-generator-webpack-plugin/-/static-site-generator-webpack-plugin-3.4.2.tgz#ad9fd0a4fb8b6f439a7a66018320b459bdb6d916"
integrity sha512-39Kn+fZDVjolLYuX5y1rDvksJIW0QEUaEC/AVO/UewNXxGzoSQI1UYnRsL+ocAcN5Yti6d6rJgEL0qZ5tNXfdw==
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
dependencies:
bluebird "^3.0.5"
cheerio "^0.22.0"
eval "^0.1.0"
url "^0.11.0"
webpack-sources "^0.2.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
"statuses@>= 1.4.0 < 2", "statuses@>= 1.5.0 < 2", statuses@~1.5.0:
version "1.5.0"
resolved "https://registry.yarnpkg.com/statuses/-/statuses-1.5.0.tgz#161c7dac177659fd9811f43771fa99381478628c"
integrity sha1-Fhx9rBd2Wf2YEfQ3cfqZOBR4Yow=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
stealthy-require@^1.1.1:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/stealthy-require/-/stealthy-require-1.1.1.tgz#35b09875b4ff49f26a777e509b3090a3226bf24b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-NbCYdbT/SfJqd35QmzCQoyJr8ks=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
stream-browserify@^2.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.0.2"
resolved "https://registry.yarnpkg.com/stream-browserify/-/stream-browserify-2.0.2.tgz#87521d38a44aa7ee91ce1cd2a47df0cb49dd660b"
integrity sha512-nX6hmklHs/gr2FuxYDltq8fJA1GDlxKQCz8O/IM4atRqBH8OORmBNgfvW5gG10GT/qQ9u0CzIvr2X5Pkt6ntqg==
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:
inherits "~2.0.1"
readable-stream "^2.0.2"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
stream-each@^1.1.0:
version "1.2.3"
resolved "https://registry.yarnpkg.com/stream-each/-/stream-each-1.2.3.tgz#ebe27a0c389b04fbcc233642952e10731afa9bae"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-vlMC2f8I2u/bZGqkdfLQW/13Zihpej/7PmSiMQsbYddxuTsJp8vRe2x2FvVExZg7FaOds43ROAuFJwPR4MTZLw==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
end-of-stream "^1.1.0"
stream-shift "^1.0.0"
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
stream-http@^2.7.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.8.3"
resolved "https://registry.yarnpkg.com/stream-http/-/stream-http-2.8.3.tgz#b2d242469288a5a27ec4fe8933acf623de6514fc"
integrity sha512-+TSkfINHDo4J+ZobQLWiMouQYB+UVYFttRA94FpEzzJ7ZdqcL4uUUQ7WkdkI4DSozGmgBUE/a47L+38PenXhUw==
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:
builtin-status-codes "^3.0.0"
inherits "^2.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
readable-stream "^2.3.6"
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
to-arraybuffer "^1.0.0"
xtend "^4.0.0"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
stream-shift@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/stream-shift/-/stream-shift-1.0.0.tgz#d5c752825e5367e786f78e18e445ea223a155952"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-1cdSgl5TZ+eG944Y5EXqIjoVWVI=
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +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
strict-uri-encode@^1.0.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/strict-uri-encode/-/strict-uri-encode-1.1.0.tgz#279b225df1d582b1f54e65addd4352e18faa0713"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-J5siXfHVgrH1TmWt3UNS4Y+qBxM=
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
Add style support to the artifacts app Test Plan: Note that the header, when rendered, is magenta. wchargin-branch: stylish-artifacts
2018-03-19 22:31:08 +00:00
string-hash@^1.1.3:
version "1.1.3"
resolved "https://registry.yarnpkg.com/string-hash/-/string-hash-1.1.3.tgz#e8aafc0ac1855b4666929ed7dd1275df5d6c811b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-6Kr8CsGFW0Zmkp7X3RJ1311sgRs=
Add style support to the artifacts app Test Plan: Note that the header, when rendered, is magenta. wchargin-branch: stylish-artifacts
2018-03-19 22:31:08 +00:00
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
string-length@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/string-length/-/string-length-2.0.0.tgz#d40dbb686a3ace960c1cffca562bf2c45f8363ed"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-1A27aGo6zpYMHP/KVivyxF+DY+0=
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:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
astral-regex "^1.0.0"
strip-ansi "^4.0.0"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
string-width@^1.0.1:
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
version "1.0.2"
resolved "https://registry.yarnpkg.com/string-width/-/string-width-1.0.2.tgz#118bdf5b8cdc51a2a7e70d211e07e2b0b9b107d3"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-EYvfW4zcUaKn5w0hHgfisLmxB9M=
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:
code-point-at "^1.0.0"
is-fullwidth-code-point "^1.0.0"
strip-ansi "^3.0.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
"string-width@^1.0.2 || 2", string-width@^2.0.0, string-width@^2.1.0, string-width@^2.1.1:
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
version "2.1.1"
resolved "https://registry.yarnpkg.com/string-width/-/string-width-2.1.1.tgz#ab93f27a8dc13d28cac815c462143a6d9012ae9e"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-nOqH59deCq9SRHlxq1Aw85Jnt4w6KvLKqWVik6oA9ZklXLNIOlqg4F2yrT1MVaTjAqvVwdfeZ7w7aCvJD7ugkw==
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:
is-fullwidth-code-point "^2.0.0"
strip-ansi "^4.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
string-width@^3.0.0, string-width@^3.1.0:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
version "3.1.0"
resolved "https://registry.yarnpkg.com/string-width/-/string-width-3.1.0.tgz#22767be21b62af1081574306f69ac51b62203961"
integrity sha512-vafcv6KjVZKSgz06oM/H6GDBrAtz8vdhQakGjFIvNrHA6y3HCF1CInLy+QLq8dTJPQ1b+KDUqDFctkdRW44e1w==
dependencies:
emoji-regex "^7.0.1"
is-fullwidth-code-point "^2.0.0"
strip-ansi "^5.1.0"
Add dependency on `commonmark` (#440) Summary: We plan to use this to more intelligently extract references from GitHub text content. See #432. Test Plan: In a Node shell, running ```js const cm = require("commonmark"); var parser = new cm.Parser(); var ast = parser.parse("Hello\nworld"); var html = new cm.HtmlRenderer({softbreak: " "}).render(ast); console.log(html); ``` prints `<p>Hello world</p>`. wchargin-branch: commonmark
2018-06-29 00:01:31 +00:00
string.prototype.repeat@^0.2.0:
version "0.2.0"
resolved "https://registry.yarnpkg.com/string.prototype.repeat/-/string.prototype.repeat-0.2.0.tgz#aba36de08dcee6a5a337d49b2ea1da1b28fc0ecf"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-q6Nt4I3O5qWjN9SbLqHaGyj8Ds8=
Add dependency on `commonmark` (#440) Summary: We plan to use this to more intelligently extract references from GitHub text content. See #432. Test Plan: In a Node shell, running ```js const cm = require("commonmark"); var parser = new cm.Parser(); var ast = parser.parse("Hello\nworld"); var html = new cm.HtmlRenderer({softbreak: " "}).render(ast); console.log(html); ``` prints `<p>Hello world</p>`. wchargin-branch: commonmark
2018-06-29 00:01:31 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
string.prototype.trim@^1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/string.prototype.trim/-/string.prototype.trim-1.1.2.tgz#d04de2c89e137f4d7d206f086b5ed2fae6be8cea"
integrity sha1-0E3iyJ4Tf019IG8Ia17S+ua+jOo=
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
define-properties "^1.1.2"
es-abstract "^1.5.0"
function-bind "^1.0.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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
string_decoder@^1.0.0, string_decoder@^1.1.1:
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
version "1.2.0"
resolved "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.2.0.tgz#fe86e738b19544afe70469243b2a1ee9240eae8d"
integrity sha512-6YqyX6ZWEYguAxgZzHGL7SsCeGx3V2TtOTqZz1xSTSWnqsbWwbptafNyvf/ACquZUXV3DANr5BDIwNYe1mN42w==
dependencies:
safe-buffer "~5.1.0"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
string_decoder@~1.1.1:
version "1.1.1"
resolved "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.1.1.tgz#9cf1611ba62685d7030ae9e4ba34149c3af03fc8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
safe-buffer "~5.1.0"
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
strip-ansi@3.0.1, strip-ansi@^3.0.0, strip-ansi@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-3.0.1.tgz#6a385fb8853d952d5ff05d0e8aaf94278dc63dcf"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-ajhfuIU9lS1f8F0Oiq+UJ43GPc8=
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:
ansi-regex "^2.0.0"
strip-ansi@^4.0.0:
version "4.0.0"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-4.0.0.tgz#a8479022eb1ac368a871389b635262c505ee368f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-qEeQIusaw2iocTibY1JixQXuNo8=
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:
ansi-regex "^3.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
strip-ansi@^5.0.0, strip-ansi@^5.1.0, strip-ansi@^5.2.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "5.2.0"
resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-5.2.0.tgz#8c9a536feb6afc962bdfa5b104a5091c1ad9c0ae"
integrity sha512-DuRs1gKbBqsMKIZlrffwlug8MHkcnpjs5VPmL1PAh+mA30U0DTotfDZ0d2UUsXpPmPmMMJ6W773MaA3J+lbiWA==
dependencies:
ansi-regex "^4.1.0"
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
strip-bom@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/strip-bom/-/strip-bom-3.0.0.tgz#2334c18e9c759f7bdd56fdef7e9ae3d588e68ed3"
integrity sha1-IzTBjpx1n3vdVv3vfprj1YjmjtM=
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
strip-eof@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/strip-eof/-/strip-eof-1.0.0.tgz#bb43ff5598a6eb05d89b59fcd129c983313606bf"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-u0P/VZim6wXYm1n80SnJgzE2Br8=
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
strip-json-comments@^2.0.1, strip-json-comments@~2.0.1:
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
version "2.0.1"
resolved "https://registry.yarnpkg.com/strip-json-comments/-/strip-json-comments-2.0.1.tgz#3c531942e908c2697c0ec344858c286c7ca0a60a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-PFMZQukIwml8DsNEhYwobHygpgo=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
supports-color@6.1.0, supports-color@^6.1.0:
version "6.1.0"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-6.1.0.tgz#0764abc69c63d5ac842dd4867e8d025e880df8f3"
integrity sha512-qe1jfm1Mg7Nq/NSh6XE24gPXROEVsWHxC1LIx//XNlD9iw7YZQGjZNjYN7xGaEG6iKdA8EtNFW6R0gjnVXp+wQ==
dependencies:
has-flag "^3.0.0"
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
supports-color@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-2.0.0.tgz#535d045ce6b6363fa40117084629995e9df324c7"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-U10EXOa2Nj+kARcIRimZXp3zJMc=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
supports-color@^5.3.0:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "5.5.0"
resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-5.5.0.tgz#e2e69a44ac8772f78a1ec0b35b689df6530efc8f"
integrity sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==
dependencies:
has-flag "^3.0.0"
Port skeleton of Odyssey frontend (#1132) This commit integrates an bare skeleton of the odyssey frontend that we implemented in the [odyssey-hackathon] repository. You can see the working frontend that we are trying to port over at [sourcecred.io/odyssey-hackathon/][scio]. The prototype in the other repository has some tooling choices which are incompatible/redundant with decisions in our codebase (sass vs aphrodite), and requires some tools not yet present here (svg-react-loader). This commit includes the build and integration work needed to port the prototype frontend into mainline SourceCred. The frontend scaffold isn't yet integrated with any "real" Odyssey data. One potential issue: right now, every page that is rendered from the SourceCred homepage is contained within a [homepage/Page], meaning that it has full SourceCred website styling, along with the SourceCred website header. The [application][scio] also has a header. Currently, I work around this by having the Odyssey UI cover up the base header (via absolute positioning), which works but is hacky. We can consider more principled solutions: - Finding a way to specify routes which aren't contained by [homepage/Page]; maybe by adding a new top-level route [here][route-alternative]. - Unify the headers for the Odyssey viewer and the page as a whole (sounds like inappropriate entanglement?) - Have a website header and also an application header (sounds ugly?) [homepage/Page]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/Page.js [route-alternative]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/createRoutes.js#L17 Test plan: Run `yarn start`, and then navigate to `localhost:8080/odyssey/`. observe that a working website is displayed, and that the cred logo next to the word "SourceCred" is loaded properly (i.e. svg-react-loader is integrated properly). Observe that there are no build/compile errors from either `yarn start` or `yarn build`. Also, observe that the UI looks passably nice, and that if the number of elements in the entity lists is larger than can be displayed, the sidebar pane scrolls independently. The UI was tested in both Chrome and Firefox. [odyssey-hackathon]: https://github.com/sourcecred/odyssey-hackathon [scio]: https://sourcecred.io/odyssey-hackathon/ Thanks to @jmnemo, as the implementation is based on [his work]. [his work]: https://github.com/jmnemo/hackathon-event/
2019-05-06 15:15:39 +00:00
svg-react-loader@^0.4.6:
version "0.4.6"
resolved "https://registry.yarnpkg.com/svg-react-loader/-/svg-react-loader-0.4.6.tgz#b263efb3e3d2fff4c682a729351aba5f185051a1"
integrity sha512-HVEypjWQsQuJdBIPzXGxpmQsQts7QwfQuYgK1rah6BVCMoLNSCh/ESKVNd7/tHq8DkWYHHTyaUMDA1FjqZYrgA==
dependencies:
css "2.2.4"
loader-utils "1.1.0"
ramda "0.21.0"
rx "4.1.0"
traverse "0.6.6"
xml2js "0.4.17"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
symbol-tree@^3.2.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.2.4"
resolved "https://registry.yarnpkg.com/symbol-tree/-/symbol-tree-3.2.4.tgz#430637d248ba77e078883951fb9aa0eed7c63fa2"
integrity sha512-9QNk5KwDF+Bvz+PyObkmSYjI5ksVUYtjW7AU22r2NKcfLJcXp96hkDWU3+XndOsUb+AQ9QhfzfCT2O+CNWT5Tw==
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 eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
table@^5.2.3:
version "5.4.1"
resolved "https://registry.yarnpkg.com/table/-/table-5.4.1.tgz#0691ae2ebe8259858efb63e550b6d5f9300171e8"
integrity sha512-E6CK1/pZe2N75rGZQotFOdmzWQ1AILtgYbMAbAjvms0S1l5IDB47zG3nCnFGB/w+7nB3vKofbLXCH7HPBo864w==
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:
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
ajv "^6.9.1"
lodash "^4.17.11"
slice-ansi "^2.1.0"
string-width "^3.0.0"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
tapable@^1.0.0, tapable@^1.1.0:
version "1.1.3"
resolved "https://registry.yarnpkg.com/tapable/-/tapable-1.1.3.tgz#a1fccc06b58db61fd7a45da2da44f5f3a3e67ba2"
integrity sha512-4WK/bYZmj8xLr+HUCODHGF1ZFzsYffasLUgEiMBY4fgtltdO6B4WJtlSbPaDTLpYTcGVwM2qLnFTICEcNxs3kA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
tar@^4, tar@^4.4.6:
Update better-sqlite3 to v5 When we took a dep on better-sqlite3 in #836, we used a fork, because better-sqlite3 did not yet support private in-memory databases via the `:memory:` filepath. As of better-sqlite3 v5, this has been added to mainline, so we no longer need the fork. The v4->v5 transition involves some breaking changes. The only ones that affected us were two field renames, from `lastUpdateROWID` to `lastUpdateRowid`, and `returnsData` to `reader`. Test plan: After updating the field accesses, `yarn test --full` passes. For added safety, I also blew away cache, loaded a nontrivial repository, and verified that the full cred workflow still works. cc @wchargin
2019-07-04 16:48:34 +00:00
version "4.4.10"
resolved "https://registry.yarnpkg.com/tar/-/tar-4.4.10.tgz#946b2810b9a5e0b26140cf78bea6b0b0d689eba1"
integrity sha512-g2SVs5QIxvo6OLp0GudTqEf05maawKUxXru104iaayWA09551tFCTI8f1Asb4lPfkBr91k07iL4c11XO3/b0tA==
dependencies:
chownr "^1.1.1"
fs-minipass "^1.2.5"
minipass "^2.3.5"
minizlib "^1.2.1"
mkdirp "^0.5.0"
safe-buffer "^5.1.2"
yallist "^3.0.3"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
terser-webpack-plugin@^1.1.0:
version "1.3.0"
resolved "https://registry.yarnpkg.com/terser-webpack-plugin/-/terser-webpack-plugin-1.3.0.tgz#69aa22426299f4b5b3775cbed8cb2c5d419aa1d4"
integrity sha512-W2YWmxPjjkUcOWa4pBEv4OP4er1aeQJlSo2UhtCFQCuRXEHjOFscO8VyWHj9JLlA0RzQb8Y2/Ta78XZvT54uGg==
dependencies:
cacache "^11.3.2"
find-cache-dir "^2.0.0"
is-wsl "^1.1.0"
loader-utils "^1.2.3"
schema-utils "^1.0.0"
serialize-javascript "^1.7.0"
source-map "^0.6.1"
terser "^4.0.0"
webpack-sources "^1.3.0"
worker-farm "^1.7.0"
terser@^4.0.0:
version "4.1.2"
resolved "https://registry.yarnpkg.com/terser/-/terser-4.1.2.tgz#b2656c8a506f7ce805a3f300a2ff48db022fa391"
integrity sha512-jvNoEQSPXJdssFwqPSgWjsOrb+ELoE+ILpHPKXC83tIxOlh2U75F1KuB2luLD/3a6/7K3Vw5pDn+hvu0C4AzSw==
dependencies:
commander "^2.20.0"
source-map "~0.6.1"
source-map-support "~0.5.12"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
test-exclude@^5.2.3:
version "5.2.3"
resolved "https://registry.yarnpkg.com/test-exclude/-/test-exclude-5.2.3.tgz#c3d3e1e311eb7ee405e092dac10aefd09091eac0"
integrity sha512-M+oxtseCFO3EDtAaGH7iiej3CBkzXqFMbzqYAACdzKui4eZA+pq3tZEwChvOdNfa7xxy8BfbmgJSIr43cC/+2g==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
glob "^7.1.3"
minimatch "^3.0.4"
read-pkg-up "^4.0.0"
require-main-filename "^2.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
text-table@0.2.0, text-table@^0.2.0:
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
version "0.2.0"
resolved "https://registry.yarnpkg.com/text-table/-/text-table-0.2.0.tgz#7f5ee823ae805207c00af2df4a84ec3fcfa570b4"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-f17oI66AUgfACvLfSoTsP8+lcLQ=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
throat@^4.0.0:
version "4.1.0"
resolved "https://registry.yarnpkg.com/throat/-/throat-4.1.0.tgz#89037cbc92c56ab18926e6ba4cbb200e15672a6a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-iQN8vJLFarGJJua6TLsgDhVnKmo=
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
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
through2@^2.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.0.5"
resolved "https://registry.yarnpkg.com/through2/-/through2-2.0.5.tgz#01c1e39eb31d07cb7d03a96a70823260b23132cd"
integrity sha512-/mrRod8xqpA+IHSLyGCQ2s8SPHiCDEeQJSep1jqLYeEUClOFG2Qsh+4FU6G9VeqpZnGW/Su8LQGc4YKni5rYSQ==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
readable-stream "~2.3.6"
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
xtend "~4.0.1"
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
through@^2.3.6:
version "2.3.8"
resolved "https://registry.yarnpkg.com/through/-/through-2.3.8.tgz#0dd4c9ffaabc357960b1b724115d7e0e86a2e1f5"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-DdTJ/6q8NXlgsbckEV1+Doai4fU=
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
thunky@^1.0.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.3"
resolved "https://registry.yarnpkg.com/thunky/-/thunky-1.0.3.tgz#f5df732453407b09191dae73e2a8cc73f381a826"
integrity sha512-YwT8pjmNcAXBZqrubu22P4FYsh2D4dxRmnWBOL8Jk8bUcRUtc5326kx32tuTmFDAZtLOGEVNl8POAR8j896Iow==
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
timers-browserify@^2.0.4:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.0.10"
resolved "https://registry.yarnpkg.com/timers-browserify/-/timers-browserify-2.0.10.tgz#1d28e3d2aadf1d5a5996c4e9f95601cd053480ae"
integrity sha512-YvC1SV1XdOUaL6gx5CoGroT3Gu49pK9+TZ38ErPldOWW4j49GI1HKs9DV+KGq/w6y+LZ72W1c8cKz2vzY+qpzg==
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:
setimmediate "^1.0.4"
tmp@^0.0.33:
version "0.0.33"
resolved "https://registry.yarnpkg.com/tmp/-/tmp-0.0.33.tgz#6d34335889768d21b2bcda0aa277ced3b1bfadf9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-jRCJlojKnZ3addtTOjdIqoRuPEKBvNXcGYqzO6zWZX8KfKEpnGY5jfggJQ3EjKuu8D4bJRr0y+cYJFmYbImXGw==
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:
os-tmpdir "~1.0.2"
tmpl@1.0.x:
version "1.0.4"
resolved "https://registry.yarnpkg.com/tmpl/-/tmpl-1.0.4.tgz#23640dd7b42d00433911140820e5cf440e521dd1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-I2QN17QtAEM5ERQIIOXPRA5SHdE=
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
to-arraybuffer@^1.0.0:
version "1.0.1"
resolved "https://registry.yarnpkg.com/to-arraybuffer/-/to-arraybuffer-1.0.1.tgz#7d229b1fcc637e466ca081180836a7aabff83f43"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-fSKbH8xjfkZsoIEYCDanqr/4P0M=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
to-fast-properties@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/to-fast-properties/-/to-fast-properties-2.0.0.tgz#dc5e698cbd079265bc73e0377681a4e4e83f616e"
integrity sha1-3F5pjL0HkmW8c+A3doGk5Og/YW4=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
to-object-path@^0.3.0:
version "0.3.0"
resolved "https://registry.yarnpkg.com/to-object-path/-/to-object-path-0.3.0.tgz#297588b7b0e7e0ac08e04e672f85c1f4999e17af"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-KXWIt7Dn4KwI4E5nL4XB9JmeF68=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
kind-of "^3.0.2"
to-regex-range@^2.1.0:
version "2.1.1"
resolved "https://registry.yarnpkg.com/to-regex-range/-/to-regex-range-2.1.1.tgz#7c80c17b9dfebe599e27367e0d4dd5590141db38"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-fIDBe53+vlmeJzZ+DU3VWQFB2zg=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
is-number "^3.0.0"
repeat-string "^1.6.1"
to-regex@^3.0.1, to-regex@^3.0.2:
version "3.0.2"
resolved "https://registry.yarnpkg.com/to-regex/-/to-regex-3.0.2.tgz#13cfdd9b336552f30b51f33a8ae1b42a7a7599ce"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-FWtleNAtZ/Ki2qtqej2CXTOayOH9bHDQF+Q48VpWyDXjbYxA4Yz8iDB31zXOBUlOHHKidDbqGVrTUvQMPmBGBw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
define-property "^2.0.2"
extend-shallow "^3.0.2"
regex-not "^1.0.2"
safe-regex "^1.1.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
toidentifier@1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/toidentifier/-/toidentifier-1.0.0.tgz#7e1be3470f1e77948bc43d94a3c8f4d7752ba553"
integrity sha512-yaOH/Pk/VEhBWWTlhI+qXxDFXlejDGcQipMlyxda9nthulaxLZUNcUqFxokp0vcYnvteJln5FNQDRrxj3YcbVw==
tough-cookie@^2.3.3, tough-cookie@^2.3.4:
version "2.5.0"
resolved "https://registry.yarnpkg.com/tough-cookie/-/tough-cookie-2.5.0.tgz#cd9fb2a0aa1d5a12b473bd9fb96fa3dcff65ade2"
integrity sha512-nlLsUzgm1kfLXSXfRZMc1KLAugd4hqJHDTvc2hDIwS3mZAfMEuMbc03SujMF+GEcpaX/qboeycw6iO8JwVv2+g==
dependencies:
psl "^1.1.28"
punycode "^2.1.1"
tough-cookie@~2.4.3:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
version "2.4.3"
resolved "https://registry.yarnpkg.com/tough-cookie/-/tough-cookie-2.4.3.tgz#53f36da3f47783b0925afa06ff9f3b165280f781"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-Q5srk/4vDM54WJsJio3XNn6K2sCG+CQ8G5Wz6bZhRZoAe/+TxjWB/GlFAnYEbkYVlON9FMk/fE3h2RLpPXo4lQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
psl "^1.1.24"
punycode "^1.4.1"
tr46@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/tr46/-/tr46-1.0.1.tgz#a8b13fd6bfd2489519674ccde55ba3693b706d09"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-qLE/1r/SSJUZZ0zN5VujaTtwbQk=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
punycode "^2.1.0"
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
Port skeleton of Odyssey frontend (#1132) This commit integrates an bare skeleton of the odyssey frontend that we implemented in the [odyssey-hackathon] repository. You can see the working frontend that we are trying to port over at [sourcecred.io/odyssey-hackathon/][scio]. The prototype in the other repository has some tooling choices which are incompatible/redundant with decisions in our codebase (sass vs aphrodite), and requires some tools not yet present here (svg-react-loader). This commit includes the build and integration work needed to port the prototype frontend into mainline SourceCred. The frontend scaffold isn't yet integrated with any "real" Odyssey data. One potential issue: right now, every page that is rendered from the SourceCred homepage is contained within a [homepage/Page], meaning that it has full SourceCred website styling, along with the SourceCred website header. The [application][scio] also has a header. Currently, I work around this by having the Odyssey UI cover up the base header (via absolute positioning), which works but is hacky. We can consider more principled solutions: - Finding a way to specify routes which aren't contained by [homepage/Page]; maybe by adding a new top-level route [here][route-alternative]. - Unify the headers for the Odyssey viewer and the page as a whole (sounds like inappropriate entanglement?) - Have a website header and also an application header (sounds ugly?) [homepage/Page]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/Page.js [route-alternative]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/createRoutes.js#L17 Test plan: Run `yarn start`, and then navigate to `localhost:8080/odyssey/`. observe that a working website is displayed, and that the cred logo next to the word "SourceCred" is loaded properly (i.e. svg-react-loader is integrated properly). Observe that there are no build/compile errors from either `yarn start` or `yarn build`. Also, observe that the UI looks passably nice, and that if the number of elements in the entity lists is larger than can be displayed, the sidebar pane scrolls independently. The UI was tested in both Chrome and Firefox. [odyssey-hackathon]: https://github.com/sourcecred/odyssey-hackathon [scio]: https://sourcecred.io/odyssey-hackathon/ Thanks to @jmnemo, as the implementation is based on [his work]. [his work]: https://github.com/jmnemo/hackathon-event/
2019-05-06 15:15:39 +00:00
traverse@0.6.6:
version "0.6.6"
resolved "https://registry.yarnpkg.com/traverse/-/traverse-0.6.6.tgz#cbdf560fd7b9af632502fed40f918c157ea97137"
integrity sha1-y99WD9e5r2MlAv7UD5GMFX6pcTc=
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
trim-right@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/trim-right/-/trim-right-1.0.1.tgz#cb2e1203067e0c8de1f614094b9fe45704ea6003"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-yy4SAwZ+DI3h9hQJS5/kVwTqYAM=
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
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
trim-trailing-lines@^1.0.0:
version "1.1.2"
resolved "https://registry.yarnpkg.com/trim-trailing-lines/-/trim-trailing-lines-1.1.2.tgz#d2f1e153161152e9f02fabc670fb40bec2ea2e3a"
integrity sha512-MUjYItdrqqj2zpcHFTkMa9WAv4JHTI6gnRQGPFLrt5L9a6tRMiDnIqYl8JBvu2d2Tc3lWJKQwlGCp0K8AvCM+Q==
trim@0.0.1:
version "0.0.1"
resolved "https://registry.yarnpkg.com/trim/-/trim-0.0.1.tgz#5858547f6b290757ee95cccc666fb50084c460dd"
integrity sha1-WFhUf2spB1fulczMZm+1AITEYN0=
trough@^1.0.0:
version "1.0.4"
resolved "https://registry.yarnpkg.com/trough/-/trough-1.0.4.tgz#3b52b1f13924f460c3fbfd0df69b587dbcbc762e"
integrity sha512-tdzBRDGWcI1OpPVmChbdSKhvSVurznZ8X36AYURAcl+0o2ldlCY2XPzyXNNxwJwwyIU+rIglTCG4kxtNKBQH7Q==
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
tslib@^1.9.0:
version "1.10.0"
resolved "https://registry.yarnpkg.com/tslib/-/tslib-1.10.0.tgz#c3c19f95973fb0a62973fb09d90d961ee43e5c8a"
integrity sha512-qOebF53frne81cf0S9B41ByenJ3/IuH8yJKngAX35CmiZySA0khhkovshKK+jGCaMnVomla7gVlIcc3EvKPbTQ==
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
tty-browserify@0.0.0:
version "0.0.0"
resolved "https://registry.yarnpkg.com/tty-browserify/-/tty-browserify-0.0.0.tgz#a157ba402da24e9bf957f9aa69d524eed42901a6"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-oVe6QC2iTpv5V/mqadUk7tQpAaY=
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
tunnel-agent@^0.6.0:
version "0.6.0"
resolved "https://registry.yarnpkg.com/tunnel-agent/-/tunnel-agent-0.6.0.tgz#27a5dea06b36b04a0a9966774b290868f0fc40fd"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-J6XeoGs2sEoKmWZ3SykIaPD8QP0=
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:
safe-buffer "^5.0.1"
tweetnacl@^0.14.3, tweetnacl@~0.14.0:
version "0.14.5"
resolved "https://registry.yarnpkg.com/tweetnacl/-/tweetnacl-0.14.5.tgz#5ae68177f192d4456269d108afa93ff8743f4f64"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-WuaBd/GS1EViadEIr6k/+HQ/T2Q=
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
type-check@~0.3.2:
version "0.3.2"
resolved "https://registry.yarnpkg.com/type-check/-/type-check-0.3.2.tgz#5884cab512cf1d355e3fb784f30804b2b520db72"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-WITKtRLPHTVeP7eE8wgEsrUg23I=
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:
prelude-ls "~1.1.2"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
type-is@~1.6.17, type-is@~1.6.18:
version "1.6.18"
resolved "https://registry.yarnpkg.com/type-is/-/type-is-1.6.18.tgz#4e552cd05df09467dcbc4ef739de89f2cf37c131"
integrity sha512-TkRKr9sUTxEH8MdfuCSP7VizJyzRNMjj2J2do2Jr3Kym598JVdEksuzPQCnlFPW4ky9Q+iA+ma9BGm06XQBy8g==
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:
media-typer "0.3.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
mime-types "~2.1.24"
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
typedarray@^0.0.6:
version "0.0.6"
resolved "https://registry.yarnpkg.com/typedarray/-/typedarray-0.0.6.tgz#867ac74e3864187b1d3d47d996a78ec5c8830777"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=
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
Add dependency on react-router^3.2.1 Summary: We’re switching from RRv4 to RRv3. We’ll remove RRv4, which is currently unused, in the next commit. wchargin-branch: add-rrv3
2018-07-21 01:30:28 +00:00
ua-parser-js@^0.7.18:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "0.7.20"
resolved "https://registry.yarnpkg.com/ua-parser-js/-/ua-parser-js-0.7.20.tgz#7527178b82f6a62a0f243d1f94fd30e3e3c21098"
integrity sha512-8OaIKfzL5cpx8eCMAhhvTlft8GYF8b2eQr6JkCyVdrgjcytyOmPCXrqXFcUnhonRpLlh5yxEZVohm6mzaowUOw==
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
uglify-js@^3.1.4:
version "3.6.0"
resolved "https://registry.yarnpkg.com/uglify-js/-/uglify-js-3.6.0.tgz#704681345c53a8b2079fb6cec294b05ead242ff5"
integrity sha512-W+jrUHJr3DXKhrsS7NUVxn3zqMOFn0hL/Ei6v0anCIMoKC93TjcflTagwIHLW7SfMFfiQuktQyFVCFHGUE0+yg==
dependencies:
commander "~2.20.0"
source-map "~0.6.1"
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
unherit@^1.0.4:
version "1.1.2"
resolved "https://registry.yarnpkg.com/unherit/-/unherit-1.1.2.tgz#14f1f397253ee4ec95cec167762e77df83678449"
integrity sha512-W3tMnpaMG7ZY6xe/moK04U9fBhi6wEiCYHUW5Mop/wQHf12+79EQGwxYejNdhEz2mkqkBlGwm7pxmgBKMVUj0w==
dependencies:
inherits "^2.0.1"
xtend "^4.0.1"
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
unicode-canonical-property-names-ecmascript@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/unicode-canonical-property-names-ecmascript/-/unicode-canonical-property-names-ecmascript-1.0.4.tgz#2619800c4c825800efdd8343af7dd9933cbe2818"
integrity sha512-jDrNnXWHd4oHiTZnx/ZG7gtUTVp+gCcTTKr8L0HjlwphROEW3+Him+IpvC+xcJEFegapiMZyZe02CyuOnRmbnQ==
unicode-match-property-ecmascript@^1.0.4:
version "1.0.4"
resolved "https://registry.yarnpkg.com/unicode-match-property-ecmascript/-/unicode-match-property-ecmascript-1.0.4.tgz#8ed2a32569961bce9227d09cd3ffbb8fed5f020c"
integrity sha512-L4Qoh15vTfntsn4P1zqnHulG0LdXgjSO035fEpdtp6YxXhMT51Q6vgM5lYdG/5X3MjS+k/Y9Xw4SFCY9IkR0rg==
dependencies:
unicode-canonical-property-names-ecmascript "^1.0.4"
unicode-property-aliases-ecmascript "^1.0.4"
unicode-match-property-value-ecmascript@^1.1.0:
version "1.1.0"
resolved "https://registry.yarnpkg.com/unicode-match-property-value-ecmascript/-/unicode-match-property-value-ecmascript-1.1.0.tgz#5b4b426e08d13a80365e0d657ac7a6c1ec46a277"
integrity sha512-hDTHvaBk3RmFzvSl0UVrUmC3PuW9wKVnpoUDYH0JDkSIovzw+J5viQmeYHxVSBptubnr7PbH2e0fnpDRQnQl5g==
unicode-property-aliases-ecmascript@^1.0.4:
version "1.0.5"
resolved "https://registry.yarnpkg.com/unicode-property-aliases-ecmascript/-/unicode-property-aliases-ecmascript-1.0.5.tgz#a9cc6cc7ce63a0a3023fc99e341b94431d405a57"
integrity sha512-L5RAqCfXqAwR3RriF8pM0lU0w4Ryf/GgzONwi6KnL1taJQa7x1TCxdJnILX59WIGOwR57IVxn7Nej0fz1Ny6fw==
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
unified@^6.1.5:
version "6.2.0"
resolved "https://registry.yarnpkg.com/unified/-/unified-6.2.0.tgz#7fbd630f719126d67d40c644b7e3f617035f6dba"
integrity sha512-1k+KPhlVtqmG99RaTbAv/usu85fcSRu3wY8X+vnsEhIxNP5VbVIDiXnLqyKIG+UMdyTg0ZX9EI6k2AfjJkHPtA==
dependencies:
bail "^1.0.0"
extend "^3.0.0"
is-plain-obj "^1.1.0"
trough "^1.0.0"
vfile "^2.0.0"
x-is-string "^0.1.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
union-value@^1.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.1"
resolved "https://registry.yarnpkg.com/union-value/-/union-value-1.0.1.tgz#0b6fe7b835aecda61c6ea4d4f02c14221e109847"
integrity sha512-tJfXmxMeWYnczCVs7XAEvIV7ieppALdyepWMkHkwciRpZraG/xwT+s2JN8+pr1+8jCRf80FFzvr+MpQeeoF4Xg==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
arr-union "^3.1.0"
get-value "^2.0.6"
is-extendable "^0.1.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
set-value "^2.0.1"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +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
uniq@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/uniq/-/uniq-1.0.1.tgz#b31c5ae8254844a3a8281541ce2b04b865a734ff"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-sxxa6CVIRKOoKBVBzisEuGWnNP8=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
unique-filename@^1.1.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.1"
resolved "https://registry.yarnpkg.com/unique-filename/-/unique-filename-1.1.1.tgz#1d69769369ada0583103a1e6ae87681b56573230"
integrity sha512-Vmp0jIp2ln35UTXuryvjzkjGdRyf9b2lTXuSYUiPmzRcl3FDtYqAwOnTJkAngD9SWhnoJzDbTKwaOrZ+STtxNQ==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
unique-slug "^2.0.0"
unique-slug@^2.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.0.2"
resolved "https://registry.yarnpkg.com/unique-slug/-/unique-slug-2.0.2.tgz#baabce91083fc64e945b0f3ad613e264f7cd4e6c"
integrity sha512-zoWr9ObaxALD3DOPfjPSqxt4fnZiWblxHIgeWqW8x7UqDzEtHEQLzji2cuJYQFCU6KmoJikOYAZlrTHHebjx2w==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
dependencies:
imurmurhash "^0.1.4"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
unist-util-is@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/unist-util-is/-/unist-util-is-3.0.0.tgz#d9e84381c2468e82629e4a5be9d7d05a2dd324cd"
integrity sha512-sVZZX3+kspVNmLWBPAB6r+7D9ZgAFPNWm66f7YNb420RlQSbn+n8rG8dGZSkrER7ZIXGQYNm5pqC3v3HopH24A==
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
unist-util-remove-position@^1.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.3"
resolved "https://registry.yarnpkg.com/unist-util-remove-position/-/unist-util-remove-position-1.1.3.tgz#d91aa8b89b30cb38bad2924da11072faa64fd972"
integrity sha512-CtszTlOjP2sBGYc2zcKA/CvNdTdEs3ozbiJ63IPBxh8iZg42SCCb8m04f8z2+V1aSk5a7BxbZKEdoDjadmBkWA==
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
dependencies:
unist-util-visit "^1.1.0"
unist-util-stringify-position@^1.0.0, unist-util-stringify-position@^1.1.1:
version "1.1.2"
resolved "https://registry.yarnpkg.com/unist-util-stringify-position/-/unist-util-stringify-position-1.1.2.tgz#3f37fcf351279dcbca7480ab5889bb8a832ee1c6"
integrity sha512-pNCVrk64LZv1kElr0N1wPiHEUoXNVFERp+mlTg/s9R5Lwg87f9bM/3sQB99w+N9D/qnM9ar3+AKDBwo/gm/iQQ==
unist-util-visit-parents@1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/unist-util-visit-parents/-/unist-util-visit-parents-1.1.2.tgz#f6e3afee8bdbf961c0e6f028ea3c0480028c3d06"
integrity sha512-yvo+MMLjEwdc3RhhPYSximset7rwjMrdt9E41Smmvg25UQIenzrN83cRnF1JMzoMi9zZOQeYXHSDf7p+IQkW3Q==
unist-util-visit-parents@^2.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.1.2"
resolved "https://registry.yarnpkg.com/unist-util-visit-parents/-/unist-util-visit-parents-2.1.2.tgz#25e43e55312166f3348cae6743588781d112c1e9"
integrity sha512-DyN5vD4NE3aSeB+PXYNKxzGsfocxp6asDc2XXE3b0ekO2BaRUpBicbbUygfSvYfUz1IkmjFR1YF7dPklraMZ2g==
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
dependencies:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
unist-util-is "^3.0.0"
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
unist-util-visit@^1.1.0, unist-util-visit@^1.3.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.4.1"
resolved "https://registry.yarnpkg.com/unist-util-visit/-/unist-util-visit-1.4.1.tgz#4724aaa8486e6ee6e26d7ff3c8685960d560b1e3"
integrity sha512-AvGNk7Bb//EmJZyhtRUnNMEpId/AZ5Ph/KUpTI09WHQuDZHKovQ1oEv3mfmKpWKtoMzyMC4GLBm1Zy5k12fjIw==
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
dependencies:
unist-util-visit-parents "^2.0.0"
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
universalify@^0.1.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "0.1.2"
resolved "https://registry.yarnpkg.com/universalify/-/universalify-0.1.2.tgz#b646f69be3942dabcecc9d6639c80dc105efaa66"
integrity sha512-rBJeI5CXAlmy1pV+617WB9J63U6XcazHHF2f2dbJix4XzpUF0RS3Zbj0FGIOCAva5P/d/GBOYaACQ1w+0azUkg==
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
unpipe@1.0.0, unpipe@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/unpipe/-/unpipe-1.0.0.tgz#b2bf4ee8514aae6165b4817829d21b2ef49904ec"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-sr9O6FFKrmFltIF4KdIbLvSZBOw=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
unset-value@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/unset-value/-/unset-value-1.0.0.tgz#8376873f7d2335179ffb1e6fc3a8ed0dfc8ab559"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-g3aHP30jNRef+x5vw6jtDfyKtVk=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
has-value "^0.3.1"
isobject "^3.0.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
upath@^1.1.1:
version "1.1.2"
resolved "https://registry.yarnpkg.com/upath/-/upath-1.1.2.tgz#3db658600edaeeccbe6db5e684d67ee8c2acd068"
integrity sha512-kXpym8nmDmlCBr7nKdIx8P2jNBa+pBpIUFRnKJ4dr8htyYGJFokkr2ZvERRtUN+9SY+JqXouNgUPtv6JQva/2Q==
uri-js@^4.2.2:
version "4.2.2"
resolved "https://registry.yarnpkg.com/uri-js/-/uri-js-4.2.2.tgz#94c540e1ff772956e2299507c010aea6c8838eb0"
integrity sha512-KY9Frmirql91X2Qgjry0Wd4Y+YTdrdZheS8TFwvkbLWf/G5KNJDCh6pKL5OZctEW4+0Baa5idK2ZQuELRwPznQ==
dependencies:
punycode "^2.1.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
urix@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/urix/-/urix-0.1.0.tgz#da937f7a62e21fec1fd18d49b35c2935067a6c72"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-2pN/emLiH+wf0Y1Js1wpNQZ6bHI=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
url-loader@^2.0.1:
version "2.0.1"
resolved "https://registry.yarnpkg.com/url-loader/-/url-loader-2.0.1.tgz#6c47fc7090e3d48939e01fe3c6efcba5938dcec5"
integrity sha512-nd+jtHG6VgYx/NnXxXSWCJ7FtHIhuyk6Pe48HKhq29Avq3r5FSdIrenvzlbb67A3SNFaQyLk0/lMZfubj0+5ww==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
loader-utils "^1.1.0"
mime "^2.4.4"
schema-utils "^1.0.0"
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
url-parse@^1.1.8, url-parse@^1.4.3:
version "1.4.7"
resolved "https://registry.yarnpkg.com/url-parse/-/url-parse-1.4.7.tgz#a8a83535e8c00a316e403a5db4ac1b9b853ae278"
integrity sha512-d3uaVyzDB9tQoSXFvuSUNFibTd9zxd2bkVrDRvF5TmvWWQwqE4lgYJ5m+x1DbecWkw+LK4RNl2CU1hHuOKPVlg==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
querystringify "^2.1.1"
requires-port "^1.0.0"
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
url@^0.11.0:
version "0.11.0"
resolved "https://registry.yarnpkg.com/url/-/url-0.11.0.tgz#3838e97cfc60521eb73c525a8e55bfdd9e2e28f1"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-ODjpfPxgUh63PFJajlW/3Z4uKPE=
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:
punycode "1.3.2"
querystring "0.2.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
use@^3.1.0:
version "3.1.1"
resolved "https://registry.yarnpkg.com/use/-/use-3.1.1.tgz#d50c8cac79a19fbc20f2911f56eb973f4e10070f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-cwESVXlO3url9YWlFW/TA9cshCEhtu7IKJ/p5soJ/gGpj7vbvFrAY/eIioQ6Dw23KjZhYgiIo8HOs1nQ2vr/oQ==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
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
util-deprecate@^1.0.1, util-deprecate@~1.0.1:
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
version "1.0.2"
resolved "https://registry.yarnpkg.com/util-deprecate/-/util-deprecate-1.0.2.tgz#450d4dc9fa70de732762fbd2d4a28981419a0ccf"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-RQ1Nyfpw3nMnYvvS1KKJgUGaDM8=
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
util.promisify@^1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/util.promisify/-/util.promisify-1.0.0.tgz#440f7165a459c9a16dc145eb8e72f35687097030"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-i+6qA2MPhvoKLuxnJNpXAGhg7HphQOSUq2LKMZD0m15EiskXUkMvKdF4Uui0WYeCUGea+o2cw/ZuwehtfsrNkA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
define-properties "^1.1.2"
object.getownpropertydescriptors "^2.0.3"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
util@0.10.3:
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
version "0.10.3"
resolved "https://registry.yarnpkg.com/util/-/util-0.10.3.tgz#7afb1afe50805246489e3db7fe0ed379336ac0f9"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-evsa/lCAUkZInj23/g7TeTNqwPk=
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:
inherits "2.0.1"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
util@^0.11.0:
version "0.11.1"
resolved "https://registry.yarnpkg.com/util/-/util-0.11.1.tgz#3236733720ec64bb27f6e26f421aaa2e1b588d61"
integrity sha512-HShAsny+zS2TZfaXxD9tYj4HQGlBezXZMZuM/S5PKLLoZkShZiGk9o5CzukI1LVHZvjdvZ2Sj1aW/Ndn2NB/HQ==
dependencies:
inherits "2.0.3"
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
utils-merge@1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/utils-merge/-/utils-merge-1.0.1.tgz#9f95710f50a267947b2ccc124741c1028427e713"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-n5VxD1CiZ5R7LMwSR0HBAoQn5xM=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
uuid@^3.0.1, uuid@^3.3.2:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.3.2"
resolved "https://registry.yarnpkg.com/uuid/-/uuid-3.3.2.tgz#1b4af4955eb3077c501c23872fc6513811587131"
integrity sha512-yXJmeNaw3DnnKAOKJE51sL/ZaYfWJRl1pK9dr19YFCu0ObS231AB1/LbqTKRAQ5kw8A90rA6fr4riOUpTZvQZA==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
v8-compile-cache@2.0.3:
version "2.0.3"
resolved "https://registry.yarnpkg.com/v8-compile-cache/-/v8-compile-cache-2.0.3.tgz#00f7494d2ae2b688cfe2899df6ed2c54bef91dbe"
integrity sha512-CNmdbwQMBjwr9Gsmohvm0pbL954tJrNzf6gWL3K+QMQf00PF7ERGrEiLgjuU3mKreLC2MeGhUsNV9ybTbLgd3w==
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
validate-npm-package-license@^3.0.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "3.0.4"
resolved "https://registry.yarnpkg.com/validate-npm-package-license/-/validate-npm-package-license-3.0.4.tgz#fc91f6b9c7ba15c857f4cb2c5defeec39d4f410a"
integrity sha512-DpKm2Ui/xN7/HQKCtpZxoRWBhZ9Z0kqtygG8XCgNQ8ZlDnxuQmWhj566j8fN4Cu3/JmbhsDo7fcAJq4s9h27Ew==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
spdx-correct "^3.0.0"
spdx-expression-parse "^3.0.0"
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
vary@~1.1.2:
version "1.1.2"
resolved "https://registry.yarnpkg.com/vary/-/vary-1.1.2.tgz#2299f02c6ded30d4a5961b0b9f74524a18f634fc"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-IpnwLG3tMNSllhsLn3RSShj2NPw=
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
verror@1.10.0:
version "1.10.0"
resolved "https://registry.yarnpkg.com/verror/-/verror-1.10.0.tgz#3a105ca17053af55d6e270c1f8288682e18da400"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-OhBcoXBTr1XW4nDB+CiGguGNpAA=
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:
assert-plus "^1.0.0"
core-util-is "1.0.2"
extsprintf "^1.2.0"
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
vfile-location@^2.0.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "2.0.5"
resolved "https://registry.yarnpkg.com/vfile-location/-/vfile-location-2.0.5.tgz#c83eb02f8040228a8d2b3f10e485be3e3433e0a2"
integrity sha512-Pa1ey0OzYBkLPxPZI3d9E+S4BmvfVwNAAXrrqGbwTVXWaX2p9kM1zZ+n35UtVM06shmWKH4RPRN8KI80qE3wNQ==
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
vfile-message@^1.0.0:
version "1.1.1"
resolved "https://registry.yarnpkg.com/vfile-message/-/vfile-message-1.1.1.tgz#5833ae078a1dfa2d96e9647886cd32993ab313e1"
integrity sha512-1WmsopSGhWt5laNir+633LszXvZ+Z/lxveBf6yhGsqnQIhlhzooZae7zV6YVM1Sdkw68dtAW3ow0pOdPANugvA==
dependencies:
unist-util-stringify-position "^1.1.1"
vfile@^2.0.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/vfile/-/vfile-2.3.0.tgz#e62d8e72b20e83c324bc6c67278ee272488bf84a"
integrity sha512-ASt4mBUHcTpMKD/l5Q+WJXNtshlWxOogYyGYYrg4lt/vuRjC1EFQtlAofL5VmtVNIZJzWYFJjzGWZ0Gw8pzW1w==
dependencies:
is-buffer "^1.1.4"
replace-ext "1.0.0"
unist-util-stringify-position "^1.0.0"
vfile-message "^1.0.0"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
vm-browserify@^1.0.1:
version "1.1.0"
resolved "https://registry.yarnpkg.com/vm-browserify/-/vm-browserify-1.1.0.tgz#bd76d6a23323e2ca8ffa12028dc04559c75f9019"
integrity sha512-iq+S7vZJE60yejDYM0ek6zg308+UZsdtPExWP9VZoCFCz1zkJoXFnAX7aZfd/ZwrkidzdUZL0C/ryW+JwAiIGw==
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
w3c-hr-time@^1.0.1:
version "1.0.1"
resolved "https://registry.yarnpkg.com/w3c-hr-time/-/w3c-hr-time-1.0.1.tgz#82ac2bff63d950ea9e3189a58a65625fedf19045"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-gqwr/2PZUOqeMYmlimViX+3xkEU=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
browser-process-hrtime "^0.1.2"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
walker@^1.0.7, walker@~1.0.5:
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
version "1.0.7"
resolved "https://registry.yarnpkg.com/walker/-/walker-1.0.7.tgz#2f7f9b8fd10d677262b18a884e28d19618e028fb"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-L3+bj9ENZ3JisYqITijRlhjgKPs=
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:
makeerror "1.0.x"
Add react-router-dom This commit adds a npm and flow-typed dependency, with no functional change. Test plan: `yarn travis` passes.
2018-05-08 19:02:17 +00:00
warning@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/warning/-/warning-3.0.0.tgz#32e5377cb572de4ab04753bdf8821c01ed605b7c"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-MuU3fLVy3kqwR1O9+IIcAe1gW3w=
Add react-router-dom This commit adds a npm and flow-typed dependency, with no functional change. Test plan: `yarn travis` passes.
2018-05-08 19:02:17 +00:00
dependencies:
loose-envify "^1.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
watchpack@^1.5.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.6.0"
resolved "https://registry.yarnpkg.com/watchpack/-/watchpack-1.6.0.tgz#4bc12c2ebe8aa277a71f1d3f14d685c7b446cd00"
integrity sha512-i6dHe3EyLjMmDlU1/bGQpEw25XSjkJULPuAVKCbNRefQVq48yXKUpwg538F7AZTf9kyr57zj++pQFltUa5H7yA==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
chokidar "^2.0.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
graceful-fs "^4.1.2"
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
neo-async "^2.5.0"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
wbuf@^1.1.0, wbuf@^1.7.3:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.7.3"
resolved "https://registry.yarnpkg.com/wbuf/-/wbuf-1.7.3.tgz#c1d8d149316d3ea852848895cb6a0bfe887b87df"
integrity sha512-O84QOnr0icsbFGLS0O3bI5FswxzRr8/gHwWkDlQFskhSPryQXvrTMxjxGP4+iWYoauLoBvfDpkrOauZ+0iZpDA==
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:
minimalistic-assert "^1.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
webidl-conversions@^4.0.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
version "4.0.2"
resolved "https://registry.yarnpkg.com/webidl-conversions/-/webidl-conversions-4.0.2.tgz#a855980b1f0b6b359ba1d5d9fb39ae941faa63ad"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-YQ+BmxuTgd6UXZW3+ICGfyqRyHXVlD5GtQr5+qjiNW7bF0cqrzX500HVXPBOvgXb5YnzDd+h0zqyv61KUD7+Sg==
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
webpack-cli@^3.3.5:
version "3.3.5"
resolved "https://registry.yarnpkg.com/webpack-cli/-/webpack-cli-3.3.5.tgz#f4d1238a66a2843d9cebf189835ea22142e72767"
integrity sha512-w0j/s42c5UhchwTmV/45MLQnTVwRoaUTu9fM5LuyOd/8lFoCNCELDogFoecx5NzRUndO0yD/gF2b02XKMnmAWQ==
dependencies:
chalk "2.4.2"
cross-spawn "6.0.5"
enhanced-resolve "4.1.0"
findup-sync "3.0.0"
global-modules "2.0.0"
import-local "2.0.0"
interpret "1.2.0"
loader-utils "1.2.3"
supports-color "6.1.0"
v8-compile-cache "2.0.3"
yargs "13.2.4"
webpack-dev-middleware@^3.7.0:
version "3.7.0"
resolved "https://registry.yarnpkg.com/webpack-dev-middleware/-/webpack-dev-middleware-3.7.0.tgz#ef751d25f4e9a5c8a35da600c5fda3582b5c6cff"
integrity sha512-qvDesR1QZRIAZHOE3iQ4CXLZZSQ1lAUsSpnQmlB1PBfoN/xdRjmge3Dok0W4IdaVLJOGJy3sGI4sZHwjRU0PCA==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
memory-fs "^0.4.1"
mime "^2.4.2"
range-parser "^1.2.1"
webpack-log "^2.0.0"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
webpack-dev-server@^3.7.2:
version "3.7.2"
resolved "https://registry.yarnpkg.com/webpack-dev-server/-/webpack-dev-server-3.7.2.tgz#f79caa5974b7f8b63268ef5421222a8486d792f5"
integrity sha512-mjWtrKJW2T9SsjJ4/dxDC2fkFVUw8jlpemDERqV0ZJIkjjjamR2AbQlr3oz+j4JLhYCHImHnXZK5H06P2wvUew==
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:
ansi-html "0.0.7"
bonjour "^3.5.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
chokidar "^2.1.6"
compression "^1.7.4"
connect-history-api-fallback "^1.6.0"
debug "^4.1.1"
del "^4.1.1"
express "^4.17.1"
html-entities "^1.2.1"
http-proxy-middleware "^0.19.1"
import-local "^2.0.0"
internal-ip "^4.3.0"
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
ip "^1.1.5"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
killable "^1.0.1"
loglevel "^1.6.3"
opn "^5.5.0"
p-retry "^3.0.1"
portfinder "^1.0.20"
schema-utils "^1.0.0"
selfsigned "^1.10.4"
semver "^6.1.1"
serve-index "^1.9.1"
sockjs "0.3.19"
sockjs-client "1.3.0"
spdy "^4.0.0"
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
strip-ansi "^3.0.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
supports-color "^6.1.0"
url "^0.11.0"
webpack-dev-middleware "^3.7.0"
webpack-log "^2.0.0"
yargs "12.0.5"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
webpack-log@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/webpack-log/-/webpack-log-2.0.0.tgz#5b7928e0637593f119d32f6227c1e0ac31e1b47f"
integrity sha512-cX8G2vR/85UYG59FgkoMamwHUIkSSlV3bBMRsbxVXVUk2j6NleCKjQ/WE9eYg9WY4w25O9w8wKP4rzNZFmUcUg==
dependencies:
ansi-colors "^3.0.0"
uuid "^3.3.2"
webpack-manifest-plugin@^2.0.4:
version "2.0.4"
resolved "https://registry.yarnpkg.com/webpack-manifest-plugin/-/webpack-manifest-plugin-2.0.4.tgz#e4ca2999b09557716b8ba4475fb79fab5986f0cd"
integrity sha512-nejhOHexXDBKQOj/5v5IZSfCeTO3x1Dt1RZEcGfBSul891X/eLIcIVH31gwxPDdsi2Z8LKKFGpM4w9+oTBOSCg==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
fs-extra "^7.0.0"
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
lodash ">=3.5 <5"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
tapable "^1.0.0"
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
Exclude node modules from backend build (#211) Setup following directions from [webpack-node-externals] [webpack-node-externals]: https://www.npmjs.com/package/webpack-node-externals This unblocks #210. Test plan: `yarn backend` still succeeds, and the binary scripts still work. The resultant binaries are much smaller, as seen below (note build time is the same). before: ``` ❯ yarn backend yarn run v1.5.1 $ node scripts/backend.js Building backend applications... Compiled successfully. File sizes after gzip: 231.37 KB bin/printCombinedGraph.js 199.5 KB bin/fetchAndPrintGithubRepo.js 46.41 KB bin/cloneAndPrintGitGraph.js 21.48 KB bin/createExampleRepo.js 17.71 KB bin/loadAndPrintGitRepository.js Build completed; results in 'bin'. Done in 4.46s. ``` after: ``` ❯ yarn backend yarn run v1.5.1 $ node scripts/backend.js Building backend applications... Compiled successfully. File sizes after gzip: 27.78 KB bin/printCombinedGraph.js 12.73 KB bin/cloneAndPrintGitGraph.js 12.41 KB bin/fetchAndPrintGithubRepo.js 6.03 KB bin/loadAndPrintGitRepository.js 5.52 KB bin/createExampleRepo.js Build completed; results in 'bin'. Done in 4.28s. ```
2018-05-04 23:31:39 +00:00
webpack-node-externals@^1.7.2:
version "1.7.2"
resolved "https://registry.yarnpkg.com/webpack-node-externals/-/webpack-node-externals-1.7.2.tgz#6e1ee79ac67c070402ba700ef033a9b8d52ac4e3"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-ajerHZ+BJKeCLviLUUmnyd5B4RavLF76uv3cs6KNuO8W+HuQaEs0y0L7o40NQxdPy5w0pcv8Ew7yPUAQG0UdCg==
Exclude node modules from backend build (#211) Setup following directions from [webpack-node-externals] [webpack-node-externals]: https://www.npmjs.com/package/webpack-node-externals This unblocks #210. Test plan: `yarn backend` still succeeds, and the binary scripts still work. The resultant binaries are much smaller, as seen below (note build time is the same). before: ``` ❯ yarn backend yarn run v1.5.1 $ node scripts/backend.js Building backend applications... Compiled successfully. File sizes after gzip: 231.37 KB bin/printCombinedGraph.js 199.5 KB bin/fetchAndPrintGithubRepo.js 46.41 KB bin/cloneAndPrintGitGraph.js 21.48 KB bin/createExampleRepo.js 17.71 KB bin/loadAndPrintGitRepository.js Build completed; results in 'bin'. Done in 4.46s. ``` after: ``` ❯ yarn backend yarn run v1.5.1 $ node scripts/backend.js Building backend applications... Compiled successfully. File sizes after gzip: 27.78 KB bin/printCombinedGraph.js 12.73 KB bin/cloneAndPrintGitGraph.js 12.41 KB bin/fetchAndPrintGithubRepo.js 6.03 KB bin/loadAndPrintGitRepository.js 5.52 KB bin/createExampleRepo.js Build completed; results in 'bin'. Done in 4.28s. ```
2018-05-04 23:31:39 +00:00
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
webpack-sources@^0.2.0:
version "0.2.3"
resolved "https://registry.yarnpkg.com/webpack-sources/-/webpack-sources-0.2.3.tgz#17c62bfaf13c707f9d02c479e0dcdde8380697fb"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-F8Yr+vE8cH+dAsR54Nzd6DgGl/s=
Add static-site-generator-webpack-plugin wchargin-branch: add-ssgwp
2018-07-21 04:27:35 +00:00
dependencies:
source-list-map "^1.1.1"
source-map "~0.5.3"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
webpack-sources@^1.3.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.3.0"
resolved "https://registry.yarnpkg.com/webpack-sources/-/webpack-sources-1.3.0.tgz#2a28dcb9f1f45fe960d8f1493252b5ee6530fa85"
integrity sha512-OiVgSrbGu7NEnEvQJJgdSFPl2qWKkWq5lHMhgiToIiN9w34EBnjYzSYs+VbL5KoYiLNtFFa7BZIKxRED3I32pA==
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:
source-list-map "^2.0.0"
source-map "~0.6.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
webpack@^4.35.3:
version "4.35.3"
resolved "https://registry.yarnpkg.com/webpack/-/webpack-4.35.3.tgz#66bc35ef215a7b75e8790f84d560013ffecf0ca3"
integrity sha512-xggQPwr9ILlXzz61lHzjvgoqGU08v5+Wnut19Uv3GaTtzN4xBTcwnobodrXE142EL1tOiS5WVEButooGzcQzTA==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
"@webassemblyjs/ast" "1.8.5"
"@webassemblyjs/helper-module-context" "1.8.5"
"@webassemblyjs/wasm-edit" "1.8.5"
"@webassemblyjs/wasm-parser" "1.8.5"
acorn "^6.2.0"
Tweak package.json - Remove obsolete eslint react app config - Pin webpack major version Test plan: yarn && yarn test
2019-07-05 18:31:37 +00:00
ajv "^6.1.0"
ajv-keywords "^3.1.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
chrome-trace-event "^1.0.0"
enhanced-resolve "^4.1.0"
eslint-scope "^4.0.0"
json-parse-better-errors "^1.0.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
loader-runner "^2.3.0"
loader-utils "^1.1.0"
memory-fs "~0.4.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
micromatch "^3.1.8"
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
mkdirp "~0.5.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
neo-async "^2.5.0"
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
node-libs-browser "^2.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
schema-utils "^1.0.0"
tapable "^1.1.0"
terser-webpack-plugin "^1.1.0"
watchpack "^1.5.0"
webpack-sources "^1.3.0"
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
websocket-driver@>=0.5.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "0.7.3"
resolved "https://registry.yarnpkg.com/websocket-driver/-/websocket-driver-0.7.3.tgz#a2d4e0d4f4f116f1e6297eba58b05d430100e9f9"
integrity sha512-bpxWlvbbB459Mlipc5GBzzZwhoZgGEZLuqPaR0INBGnPAY1vdBX6hPnoFXiw+3yWxDuHyQjO2oXTMyS8A5haFg==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
http-parser-js ">=0.4.0 <0.4.11"
safe-buffer ">=5.1.0"
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
websocket-extensions ">=0.1.1"
websocket-extensions@>=0.1.1:
version "0.1.3"
resolved "https://registry.yarnpkg.com/websocket-extensions/-/websocket-extensions-0.1.3.tgz#5d2ff22977003ec687a4b87073dfbbac146ccf29"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-nqHUnMXmBzT0w570r2JpJxfiSD1IzoI+HGVdd3aZ0yNi3ngvQ4jv1dtHt5VGxfI2yj5yqImPhOK4vmIh2xMbGg==
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
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
whatwg-encoding@^1.0.1, whatwg-encoding@^1.0.3:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.0.5"
resolved "https://registry.yarnpkg.com/whatwg-encoding/-/whatwg-encoding-1.0.5.tgz#5abacf777c32166a51d085d6b4f3e7d27113ddb0"
integrity sha512-b5lim54JOPN9HtzvK9HFXvBma/rnfFeqsic0hSpjtDbVxR3dJKLc+KB4V6GgiGOvl7CY/KNh8rxSo9DKQrnUEw==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
iconv-lite "0.4.24"
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
whatwg-fetch@2.0.3:
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
version "2.0.3"
resolved "https://registry.yarnpkg.com/whatwg-fetch/-/whatwg-fetch-2.0.3.tgz#9c84ec2dcf68187ff00bc64e1274b442176e1c84"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-nITsLc9oGH/wC8ZOEnS0QhduHIQ=
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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
whatwg-fetch@2.0.4:
version "2.0.4"
resolved "https://registry.yarnpkg.com/whatwg-fetch/-/whatwg-fetch-2.0.4.tgz#dde6a5df315f9d39991aa17621853d720b85566f"
integrity sha512-dcQ1GWpOD/eEQ97k66aiEVpNnapVj90/+R+SXTPYGHpYBBypfKJEQjLrvMZ7YXbKm21gXd4NcuxUTjiv1YtLng==
whatwg-fetch@>=0.10.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/whatwg-fetch/-/whatwg-fetch-3.0.0.tgz#fc804e458cc460009b1a2b966bc8817d2578aefb"
integrity sha512-9GSJUgz1D4MfyKU7KRqwOjXCXTqWdFNvEr7eUBYchQiVc744mqK/MzXPNR2WsPkmkOa4ywfg8C2n8h+13Bey1Q==
whatwg-mimetype@^2.1.0, whatwg-mimetype@^2.2.0:
version "2.3.0"
resolved "https://registry.yarnpkg.com/whatwg-mimetype/-/whatwg-mimetype-2.3.0.tgz#3d4b1e0312d2079879f826aff18dbeeca5960fbf"
integrity sha512-M4yMwr6mAnQz76TbJm914+gPpB/nCwvZbJU28cUD6dR004SAxDLOOSUaB1JDRqLtaOV/vi0IC5lEAGFgrjGv/g==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
whatwg-url@^6.4.1:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
version "6.5.0"
resolved "https://registry.yarnpkg.com/whatwg-url/-/whatwg-url-6.5.0.tgz#f2df02bff176fd65070df74ad5ccbb5a199965a8"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-rhRZRqx/TLJQWUpQ6bmrt2UV4f0HCQ463yQuONJqC6fO2VoEb1pTYddbe59SkYq87aoM5A3bdhMZiUiVws+fzQ==
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:
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
lodash.sortby "^4.7.0"
tr46 "^1.0.1"
webidl-conversions "^4.0.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
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
whatwg-url@^7.0.0:
version "7.0.0"
resolved "https://registry.yarnpkg.com/whatwg-url/-/whatwg-url-7.0.0.tgz#fde926fa54a599f3adf82dff25a9f7be02dc6edd"
integrity sha512-37GeVSIJ3kn1JgKyjiYNmSLP1yzbpb29jdmwBSgkD9h40/hyrR/OifpVUndji3tmwGgD8qpw7iQu3RSbCrBpsQ==
dependencies:
lodash.sortby "^4.7.0"
tr46 "^1.0.1"
webidl-conversions "^4.0.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
which-module@^2.0.0:
version "2.0.0"
resolved "https://registry.yarnpkg.com/which-module/-/which-module-2.0.0.tgz#d9ef07dce77b9902b8a3a8fa4b31c3e3f7e6e87a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-2e8H3Od7mQK4o6j6SzHD4/fm6Ho=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
which@^1.2.14, which@^1.2.9, which@^1.3.0, which@^1.3.1:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.3.1"
resolved "https://registry.yarnpkg.com/which/-/which-1.3.1.tgz#a45043d54f5805316da8d62f9f50918d3da70b0a"
integrity sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==
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:
isexe "^2.0.0"
wide-align@^1.1.0:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
version "1.1.3"
resolved "https://registry.yarnpkg.com/wide-align/-/wide-align-1.1.3.tgz#ae074e6bdc0c14a431e804e624549c633b000457"
integrity sha512-QGkOQc8XL6Bt5PwnsExKBPuMKBxnGxWWW3fU55Xt4feHozMUhdUMaBCk290qpm/wG5u/RSKzwdAC4i51YigihA==
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:
Mass update of dependencies This commit deletes and regenerates the `yarn.lock` file, with the effect that all dependencies are upaded to the latest version allowed by our package.json. (For example, if we are pinned to `^2.4.0`, we might now get `2.6.3`.) This commit was generated via: ```Bash $ rm yarn.lock $ yarn ``` Test plan: `yarn test --full` passes, and I also manually tested the frontend.
2019-07-05 16:26:24 +00:00
string-width "^1.0.2 || 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
wordwrap@~0.0.2:
version "0.0.3"
resolved "https://registry.yarnpkg.com/wordwrap/-/wordwrap-0.0.3.tgz#a3d5da6cd5c0bc0008d37234bbaf1bed63059107"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-o9XabNXAvAAI03I0u68b7WMFkQc=
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
wordwrap@~1.0.0:
version "1.0.0"
resolved "https://registry.yarnpkg.com/wordwrap/-/wordwrap-1.0.0.tgz#27584810891456a4171c8d0226441ade90cbcaeb"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-J1hIEIkUVqQXHI0CJkQa3pDLyus=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
worker-farm@^1.7.0:
version "1.7.0"
resolved "https://registry.yarnpkg.com/worker-farm/-/worker-farm-1.7.0.tgz#26a94c5391bbca926152002f69b84a4bf772e5a8"
integrity sha512-rvw3QTZc8lAxyVrqcSGVm5yP/IJ2UcB3U0graE3LCFoZ0Yn2x4EoVSqJKdB/T5M+FLcRPjz4TDacRf3OCfNUzw==
dependencies:
errno "~0.1.7"
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
wrap-ansi@^2.0.0:
version "2.1.0"
resolved "https://registry.yarnpkg.com/wrap-ansi/-/wrap-ansi-2.1.0.tgz#d8fc3d284dd05794fe84973caecdd1cf824fdd85"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-2Pw9KE3QV5T+hJc8rs3Rz4JP3YU=
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:
string-width "^1.0.1"
strip-ansi "^3.0.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
wrap-ansi@^5.1.0:
version "5.1.0"
resolved "https://registry.yarnpkg.com/wrap-ansi/-/wrap-ansi-5.1.0.tgz#1fd1f67235d5b6d0fee781056001bfb694c03b09"
integrity sha512-QC1/iN/2/RPVJ5jYK8BGttj5z83LmSKmvbvrXPNCLZSEb32KKVDJDl/MOt2N01qU2H/FkzEa9PKto1BqDjtd7Q==
dependencies:
ansi-styles "^3.2.0"
string-width "^3.0.0"
strip-ansi "^5.0.0"
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
wrappy@1:
version "1.0.2"
resolved "https://registry.yarnpkg.com/wrappy/-/wrappy-1.0.2.tgz#b5243d8f3ec1aa35f1364605bc0d1036e30ab69f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-tSQ9jz7BqjXxNkYFvA0QNuMKtp8=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
write-file-atomic@2.4.1:
version "2.4.1"
resolved "https://registry.yarnpkg.com/write-file-atomic/-/write-file-atomic-2.4.1.tgz#d0b05463c188ae804396fd5ab2a370062af87529"
integrity sha512-TGHFeZEZMnv+gBFRfjAcxL5bPHrsGKtnb4qsFAws7/vlh+QfwAaySIw4AXP9ZskTTh5GWu3FLuJhsWVdiJPGvg==
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:
graceful-fs "^4.1.11"
imurmurhash "^0.1.4"
signal-exit "^3.0.2"
Update eslint and eslint configuration This commit updates eslint from v4 to v6. In doing so, I've moved off of the create-react-app base eslint config. We were on an old version (v2) and it doesn't make sense to update to v4, as in v4 create-react-app uses typescript. Also, it didn't make sense to stay on create-react-app's v2 config, because then it had unmet peer dependency constraints on old versions of eslint. Instead, I've moved us to use the default rules for eslint, eslint-plugin-react, and eslint-plugin-flowtype. I also made some changes to the codebase to satisfy the new lint rules that came with this change. Test plan: `yarn test` passes.
2019-07-05 17:36:43 +00:00
write@1.0.3:
version "1.0.3"
resolved "https://registry.yarnpkg.com/write/-/write-1.0.3.tgz#0800e14523b923a387e415123c865616aae0f5c3"
integrity sha512-/lg70HAjtkUgWPVZhZcm+T4hkL8Zbtp1nFNOn3lRrxnlv50SRBv7cR7RqR+GMsd3hUXy9hWBo4CHTbFTcOYwig==
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:
mkdirp "^0.5.1"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
ws@^5.2.0:
version "5.2.2"
resolved "https://registry.yarnpkg.com/ws/-/ws-5.2.2.tgz#dffef14866b8e8dc9133582514d1befaf96e980f"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-jaHFD6PFv6UgoIVda6qZllptQsMlDEJkTQcybzzXDYM1XO9Y8em691FGMPmM46WGyLU4z9KMgQN+qrux/nhlHA==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
async-limiter "~1.0.0"
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
x-is-string@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/x-is-string/-/x-is-string-0.1.0.tgz#474b50865af3a49a9c4657f05acd145458f77d82"
integrity sha1-R0tQhlrzpJqcRlfwWs0UVFj3fYI=
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
xml-name-validator@^3.0.0:
version "3.0.0"
resolved "https://registry.yarnpkg.com/xml-name-validator/-/xml-name-validator-3.0.0.tgz#6ae73e06de4d8c6e47f9fb181f78d648ad457c6a"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-A5CUptxDsvxKJEU3yO6DuWBSJz/qizqzJKOMIfUJHETbBw/sFaDxgd6fxm1ewUaM0jZ444Fc5vC5ROYurg/4Pw==
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
Port skeleton of Odyssey frontend (#1132) This commit integrates an bare skeleton of the odyssey frontend that we implemented in the [odyssey-hackathon] repository. You can see the working frontend that we are trying to port over at [sourcecred.io/odyssey-hackathon/][scio]. The prototype in the other repository has some tooling choices which are incompatible/redundant with decisions in our codebase (sass vs aphrodite), and requires some tools not yet present here (svg-react-loader). This commit includes the build and integration work needed to port the prototype frontend into mainline SourceCred. The frontend scaffold isn't yet integrated with any "real" Odyssey data. One potential issue: right now, every page that is rendered from the SourceCred homepage is contained within a [homepage/Page], meaning that it has full SourceCred website styling, along with the SourceCred website header. The [application][scio] also has a header. Currently, I work around this by having the Odyssey UI cover up the base header (via absolute positioning), which works but is hacky. We can consider more principled solutions: - Finding a way to specify routes which aren't contained by [homepage/Page]; maybe by adding a new top-level route [here][route-alternative]. - Unify the headers for the Odyssey viewer and the page as a whole (sounds like inappropriate entanglement?) - Have a website header and also an application header (sounds ugly?) [homepage/Page]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/Page.js [route-alternative]: https://github.com/sourcecred/sourcecred/blob/ee1d2fb996718fe41325711271542a54c197a1ed/src/homepage/createRoutes.js#L17 Test plan: Run `yarn start`, and then navigate to `localhost:8080/odyssey/`. observe that a working website is displayed, and that the cred logo next to the word "SourceCred" is loaded properly (i.e. svg-react-loader is integrated properly). Observe that there are no build/compile errors from either `yarn start` or `yarn build`. Also, observe that the UI looks passably nice, and that if the number of elements in the entity lists is larger than can be displayed, the sidebar pane scrolls independently. The UI was tested in both Chrome and Firefox. [odyssey-hackathon]: https://github.com/sourcecred/odyssey-hackathon [scio]: https://sourcecred.io/odyssey-hackathon/ Thanks to @jmnemo, as the implementation is based on [his work]. [his work]: https://github.com/jmnemo/hackathon-event/
2019-05-06 15:15:39 +00:00
xml2js@0.4.17:
version "0.4.17"
resolved "https://registry.yarnpkg.com/xml2js/-/xml2js-0.4.17.tgz#17be93eaae3f3b779359c795b419705a8817e868"
integrity sha1-F76T6q4/O3eTWceVtBlwWogX6Gg=
dependencies:
sax ">=0.6.0"
xmlbuilder "^4.1.0"
xmlbuilder@^4.1.0:
version "4.2.1"
resolved "https://registry.yarnpkg.com/xmlbuilder/-/xmlbuilder-4.2.1.tgz#aa58a3041a066f90eaa16c2f5389ff19f3f461a5"
integrity sha1-qlijBBoGb5DqoWwvU4n/GfP0YaU=
dependencies:
lodash "^4.0.0"
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
xtend@^4.0.0, xtend@^4.0.1, xtend@~4.0.1:
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
version "4.0.1"
resolved "https://registry.yarnpkg.com/xtend/-/xtend-4.0.1.tgz#a5c6d532be656e23db820efb943a1f04998d63af"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-pcbVMr5lbiPbgg77lDofBJmNY68=
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
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
"y18n@^3.2.1 || ^4.0.0", y18n@^4.0.0:
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +00:00
version "4.0.0"
resolved "https://registry.yarnpkg.com/y18n/-/y18n-4.0.0.tgz#95ef94f85ecc81d007c264e190a120f0a3c8566b"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha512-r9S/ZyXu/Xu9q1tYlpsLIsa3EeLXXk0VwlxqTcFRfg9EhMW+17kbt9G0NrgCmhGb5vT2hyhJZLfDGx+7+5Uj/w==
Add a favicon (#637) Summary: In addition to the obvious benefit of having a favicon, this gets rid of a 404 Not Found error on our home page, tremendously boosting our hacker cred. Test Plan: The favicon is displayed in both `yarn start` and the static site (as a result of the build script). The added build test fails before this change. wchargin-branch: add-favicon
2018-08-10 20:15:49 +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
yallist@^2.1.2:
version "2.1.2"
resolved "https://registry.yarnpkg.com/yallist/-/yallist-2.1.2.tgz#1c11f9218f076089a47dd512f93c6699a6a81d52"
Add integrity lines to yarn lockfile (#941) Generated by running `yarn` with version 1.10
2018-10-29 20:59:13 +00:00
integrity sha1-HBH5IY8HYImkfdUS+TxmmaaoHVI=
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
yallist@^3.0.0, yallist@^3.0.2, yallist@^3.0.3:
Update better-sqlite3 to v5 When we took a dep on better-sqlite3 in #836, we used a fork, because better-sqlite3 did not yet support private in-memory databases via the `:memory:` filepath. As of better-sqlite3 v5, this has been added to mainline, so we no longer need the fork. The v4->v5 transition involves some breaking changes. The only ones that affected us were two field renames, from `lastUpdateROWID` to `lastUpdateRowid`, and `returnsData` to `reader`. Test plan: After updating the field accesses, `yarn test --full` passes. For added safety, I also blew away cache, loaded a nontrivial repository, and verified that the full cred workflow still works. cc @wchargin
2019-07-04 16:48:34 +00:00
version "3.0.3"
resolved "https://registry.yarnpkg.com/yallist/-/yallist-3.0.3.tgz#b4b049e314be545e3ce802236d6cd22cd91c3de9"
integrity sha512-S+Zk8DEWE6oKpV+vI3qWkaK+jSbIK86pCwe2IF/xwIpQ8jEuxpw9NyaGjmp9+BoJv5FV2piqCDcoCtStppiq2A==
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
yargs-parser@^11.1.1:
version "11.1.1"
resolved "https://registry.yarnpkg.com/yargs-parser/-/yargs-parser-11.1.1.tgz#879a0865973bca9f6bab5cbdf3b1c67ec7d3bcf4"
integrity sha512-C6kB/WJDiaxONLJQnF8ccx9SEeoTTLek8RVbaOIsrAUS8VrBEXfmeSnCZxygc+XC2sNMBIwOOnfcxiynjHsVSQ==
dependencies:
camelcase "^5.0.0"
decamelize "^1.2.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
yargs-parser@^13.1.0:
version "13.1.1"
resolved "https://registry.yarnpkg.com/yargs-parser/-/yargs-parser-13.1.1.tgz#d26058532aa06d365fe091f6a1fc06b2f7e5eca0"
integrity sha512-oVAVsHz6uFrg3XQheFII8ESO2ssAf9luWuAd6Wexsu4F3OtIW0o8IribPXYrD4WC24LWtPrJlGy87y5udK+dxQ==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
camelcase "^5.0.0"
decamelize "^1.2.0"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
yargs@12.0.5, yargs@^12.0.2:
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
version "12.0.5"
resolved "https://registry.yarnpkg.com/yargs/-/yargs-12.0.5.tgz#05f5997b609647b64f66b81e3b4b10a368e7ad13"
integrity sha512-Lhz8TLaYnxq/2ObqHDql8dX8CJi97oHxrjUcYtzKbbykPtVW9WB+poxI+NM2UIzsMgNCZTIf0AQwsjK5yMAqZw==
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
dependencies:
cliui "^4.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
decamelize "^1.2.0"
find-up "^3.0.0"
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
get-caller-file "^1.0.1"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
os-locale "^3.0.0"
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
require-directory "^2.1.1"
require-main-filename "^1.0.1"
set-blocking "^2.0.0"
Upgrade jest to 23.4.1 (#537) Flow types regenerated via flow-typed install jest@23.4.1 Test plan: Travis
2018-07-27 19:28:04 +00:00
string-width "^2.0.0"
which-module "^2.0.0"
Upgrade jest from v23 to v24 Just some general housekeeping. `yarn test --full` passes without issue.
2019-07-04 17:53:48 +00:00
y18n "^3.2.1 || ^4.0.0"
yargs-parser "^11.1.1"
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
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
yargs@13.2.4:
version "13.2.4"
resolved "https://registry.yarnpkg.com/yargs/-/yargs-13.2.4.tgz#0b562b794016eb9651b98bd37acf364aa5d6dc83"
integrity sha512-HG/DWAJa1PAnHT9JAhNa8AbAv3FPaiLzioSjCcmuXXhP8MlpHO5vwls4g4j6n30Z74GVQj8Xa62dWVx1QCGklg==
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:
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
cliui "^5.0.0"
find-up "^3.0.0"
get-caller-file "^2.0.1"
os-locale "^3.1.0"
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
require-directory "^2.1.1"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
require-main-filename "^2.0.0"
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
set-blocking "^2.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
string-width "^3.0.0"
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
which-module "^2.0.0"
upgrade to webpack 4 Now that babel is upgraded, upgrading webpack was pretty straightforward. - We take advantage of the new `mode` config option, and no longer need to manually set up Uglify plugin - Uglifyjs is back, I checked the prod build output: it's very ugly - I updated the RemoveBuildDirectoryPlugin per instructions, and verified it still works. - I verified that of `yarn backend`, `yarn build`, and `yarn start` all still work as expected.
2019-07-11 04:41:26 +00:00
y18n "^4.0.0"
yargs-parser "^13.1.0"