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

122 lines
3.3 KiB
JSON
Raw Normal View History

Frontend setup (#13) * Initial infrastructure for sourcecred-explorer. Setup npm, yarn, flow, jest using scaffolding from create-react-app. - used create-react-app to get the basic pieces - added support for flow via instructions in the create-react-app user guide - added flow-typed so that flow+jest will work well * Add some additional resources * Add index.css * Remove .DS_STORE per @wchargin's suggestion
2018-02-16 22:32:24 +00:00
{
"name": "sourcecred-explorer",
"version": "0.1.0",
"private": true,
"dependencies": {
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",
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"autoprefixer": "7.1.6",
"babel-core": "6.26.0",
"babel-eslint": "7.2.3",
"babel-jest": "20.0.3",
"babel-loader": "7.1.2",
"babel-preset-react-app": "^3.1.1",
"babel-runtime": "6.26.0",
"case-sensitive-paths-webpack-plugin": "2.1.1",
"chalk": "1.1.3",
"css-loader": "0.28.7",
"dotenv": "4.0.0",
"dotenv-expand": "4.0.1",
"eslint": "4.10.0",
"eslint-config-react-app": "^2.1.0",
"eslint-loader": "1.9.0",
"eslint-plugin-flowtype": "2.39.1",
"eslint-plugin-import": "2.8.0",
"eslint-plugin-jsx-a11y": "5.1.1",
"eslint-plugin-react": "7.4.0",
"extract-text-webpack-plugin": "3.0.2",
"file-loader": "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
"flow-bin": "^0.65.0",
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"fs-extra": "3.0.1",
"html-webpack-plugin": "2.29.0",
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
"husky": "^0.14.3",
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.2.1",
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"jest": "20.0.4",
Fetch GitHub repos using the GitHub v4 API (#75) Summary: It’s a whole new world of GraphQL! Our parser is now just a GraphQL query that asks for exactly what we want and dumps it to a file. The data exposed by the v4 API is also in a much nicer format than that of the v3 API, so this is pretty much a universal improvement. Currently, we do not handle pagination. We require that the repository in question have fewer than a fixed number of issues, and comments per issue, and reviews per PR, and review comments per PR, and so on. If this limit is exceeded, the script will fail-fast with a nice error message. To fix this, we’ll need to write a general-purpose pagination API that allows traversing cursors at any level of the query. Paired with @wchargin. Test Plan: Run $ GITHUB_TOKEN="your_token_here" src/backend/fetchGitHubRepoTest.sh and verify that it exits with 0. Note that if you change this script’s repository from `tiny-example-repository` to `sourcecred`, the script correctly fails and outputs a useful diff. wchargin-branch: github-v4-graphql
2018-03-15 21:56:25 +00:00
"json-stable-stringify": "^1.0.1",
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
"lint-staged": "^6.1.1",
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",
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"object-assign": "4.1.1",
"postcss-flexbugs-fixes": "3.2.0",
"postcss-loader": "2.0.8",
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
"prettier": "^1.10.2",
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"promise": "8.0.1",
"raf": "3.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
"react": "^16.2.0",
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"react-dev-utils": "^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
"react-dom": "^16.2.0",
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"style-loader": "0.19.0",
"sw-precache-webpack-plugin": "0.11.4",
"url-loader": "0.6.2",
"webpack": "3.8.1",
"webpack-dev-server": "2.9.4",
"webpack-manifest-plugin": "1.3.2",
"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
},
"scripts": {
Set up prettier as an autoformatter (#18) Setup prettier precommit, with yarn prettify to reformat. - Prettier runs as a precommit hook and fails if code is improperly formatted. - Run `yarn prettify` to reformat the project.
2018-02-18 09:59:28 +00:00
"precommit": "npm run lint-staged",
"lint-staged": "lint-staged",
"prettify": "prettier --write '**/*.js'",
Setup travis CI testing (#58) Observe that it passed on this commit, but failed builds [#2: Break Tests][2], [#3: Break Flow][3], and [#4: Break Prettier][4]. Close #23 [2]: https://travis-ci.org/sourcecred/sourcecred/builds/348453195 [3]: https://travis-ci.org/sourcecred/sourcecred/builds/348454983 [4]: https://travis-ci.org/sourcecred/sourcecred/builds/348455387
2018-03-02 22:39:54 +00:00
"check-pretty": "prettier --list-different '**/*.js'",
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"start": "node scripts/start.js",
"build": "node scripts/build.js",
Configure Webpack for backend applications (#84) Summary: Running `yarn backend` will now bundle backend applications. They’ll be placed into the new `bin/` directory. This enables us to use ES6 modules with the standard syntax, Flow types, and all the other goodies that we’ve come to expect. A backend build takes about 2.5s on my laptop. Created by forking the prod configuration to a backend configuration and trimming it down appropriately. To test out the new changes, this commit changes `fetchGitHubRepo` and its driver to use the ES6 module system and Flow types, both of which are properly resolved. Test Plan: Run `yarn backend`. Then, you can directly run an entry point via ``` $ node bin/fetchAndPrintGitHubRepo.js sourcecred example-repo "${TOKEN}" ``` or invoke the standard test driver via ```shell $ GITHUB_TOKEN="${TOKEN}" src/backend/fetchGitHubRepoTest.sh ``` where `${TOKEN}` is your GitHub authentication token. wchargin-branch: webpack-backend
2018-03-19 05:43:23 +00:00
"backend": "node scripts/backend.js",
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"test": "node scripts/test.js --env=jsdom",
Setup travis CI testing (#58) Observe that it passed on this commit, but failed builds [#2: Break Tests][2], [#3: Break Flow][3], and [#4: Break Prettier][4]. Close #23 [2]: https://travis-ci.org/sourcecred/sourcecred/builds/348453195 [3]: https://travis-ci.org/sourcecred/sourcecred/builds/348454983 [4]: https://travis-ci.org/sourcecred/sourcecred/builds/348455387
2018-03-02 22:39:54 +00:00
"flow": "flow",
"travis": "npm run check-pretty && npm run flow && CI=true npm run test"
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
},
Add "license" field to package.json (#52)
2018-03-02 19:31:12 +00:00
"license": "MIT",
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
"lint-staged": {
"**/*.js": "prettier --list-different"
},
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"jest": {
"collectCoverageFrom": [
"src/**/*.{js,jsx,mjs}"
],
"setupFiles": [
"<rootDir>/config/polyfills.js"
],
"testMatch": [
"<rootDir>/src/**/__tests__/**/*.{js,jsx,mjs}",
"<rootDir>/src/**/?(*.)(spec|test).{js,jsx,mjs}"
],
"testEnvironment": "node",
"testURL": "http://localhost",
"transform": {
"^.+\\.(js|jsx|mjs)$": "<rootDir>/node_modules/babel-jest",
"^.+\\.css$": "<rootDir>/config/jest/cssTransform.js",
"^(?!.*\\.(js|jsx|mjs|css|json)$)": "<rootDir>/config/jest/fileTransform.js"
},
"transformIgnorePatterns": [
"[/\\\\]node_modules[/\\\\].+\\.(js|jsx|mjs)$"
],
"moduleNameMapper": {
"^react-native$": "react-native-web"
},
"moduleFileExtensions": [
"web.js",
"mjs",
"js",
"json",
"web.jsx",
"jsx",
"node"
]
},
"babel": {
Autogenerate PropTypes from Flow types (#20) Summary: Closes #17; see discussion there. This commit uses the `babel-plugin-flow-react-proptypes` package to automatically create PropType definitions from components that are typed with Flow. It simultaneously updates all of our existing components to be typed with Flow. As a result, we have both static and dynamic type checking. Test Plan: Note that `yarn test` and `yarn flow` report no errors, and that there are no prop validation errors at runtime with `yarn start`. Then, apply the following patch: ```diff diff --git a/explorer/src/UserExplorer.js b/explorer/src/UserExplorer.js index bb574cd..636a10d 100644 --- a/explorer/src/UserExplorer.js +++ b/explorer/src/UserExplorer.js @@ -18,7 +18,7 @@ export class UserExplorer extends Component<{ .sort((a,b) => b[1] - a[1]); const entries = sortedUserWeightTuples.map(authorWeight => { const [author, weight] = authorWeight; - return <UserEntry userId={author} weight={weight} key={author}/> + return <UserEntry userId={55} weight={weight} key={author}/> }); return <div className="user-explorer"> <h3> User Explorer </h3> ``` Note that `yarn test` fails (the `App.test.js` E2E rendering test), `yarn flow` fails, and there is a runtime prop validation error. wchargin-branch: autogenerate-proptypes
2018-02-17 21:30:16 +00:00
"plugins": [
"flow-react-proptypes"
],
Eject from create-react-app (#19) Summary: This commit was created by performing the following steps: - `rm -r node_modules` - `yarn install` - `yarn eject` - `rm -r node_modules` - `yarn install` on an environment wit Node v6.11.1. The final `rm -r node_modules && yarn install` ensures that the `yarn.lock` file is updated accordingly. Test Plan: `yarn test`, `yarn flow`, and `yarn start` all still do the right thing. wchargin-branch: eject
2018-02-17 21:28:47 +00:00
"presets": [
"react-app"
]
},
"eslintConfig": {
"extends": "react-app"
Autogenerate PropTypes from Flow types (#20) Summary: Closes #17; see discussion there. This commit uses the `babel-plugin-flow-react-proptypes` package to automatically create PropType definitions from components that are typed with Flow. It simultaneously updates all of our existing components to be typed with Flow. As a result, we have both static and dynamic type checking. Test Plan: Note that `yarn test` and `yarn flow` report no errors, and that there are no prop validation errors at runtime with `yarn start`. Then, apply the following patch: ```diff diff --git a/explorer/src/UserExplorer.js b/explorer/src/UserExplorer.js index bb574cd..636a10d 100644 --- a/explorer/src/UserExplorer.js +++ b/explorer/src/UserExplorer.js @@ -18,7 +18,7 @@ export class UserExplorer extends Component<{ .sort((a,b) => b[1] - a[1]); const entries = sortedUserWeightTuples.map(authorWeight => { const [author, weight] = authorWeight; - return <UserEntry userId={author} weight={weight} key={author}/> + return <UserEntry userId={55} weight={weight} key={author}/> }); return <div className="user-explorer"> <h3> User Explorer </h3> ``` Note that `yarn test` fails (the `App.test.js` E2E rendering test), `yarn flow` fails, and there is a runtime prop validation error. wchargin-branch: autogenerate-proptypes
2018-02-17 21:30:16 +00:00
},
"devDependencies": {
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
"babel-plugin-flow-react-proptypes": "^18.0.0",
"enzyme": "^3.3.0",
"enzyme-adapter-react-16": "^1.1.1",
"enzyme-to-json": "^3.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
}
}