empayre/fleet
14
0
Fork 0
mirror of https://github.com/empayre/fleet.git synced 2024-11-06 08:55:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
1d5596941a
fleet/package.json

87 lines
2.2 KiB
JSON
Raw Normal View History

React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. **Note:** Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications
2016-08-10 05:15:44 +00:00
{
"name": "Kolide",
"version": "0.1.0",
"description": "Kolide, Black Box Security. Unboxed",
"author": "Kolide, Inc.",
"private": "true",
Testing/linting setup (#120)
2016-09-06 18:41:16 +00:00
"scripts": {
Making JS tests windows friendly (#123)
2016-09-06 21:00:34 +00:00
"lint": "make lint-js",
"test": "make test-js"
Testing/linting setup (#120)
2016-09-06 18:41:16 +00:00
},
React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. **Note:** Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications
2016-08-10 05:15:44 +00:00
"dependencies": {
"autoprefixer": "6.3.7",
"autoprefixer-loader": "^3.2.0",
"babel-core": "6.11.4",
"babel-eslint": "6.1.2",
"babel-loader": "6.2.4",
"babel-preset-es2015": "6.9.0",
"babel-preset-es2016": "6.11.3",
"babel-preset-react": "6.11.1",
"babel-preset-react-hmre": "1.1.1",
"babel-preset-stage-0": "6.5.0",
"css-loader": "^0.23.1",
"cssrecipes-defaults": "^0.5.0",
Testing/linting setup (#120)
2016-09-06 18:41:16 +00:00
"enzyme": "^2.4.1",
React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. **Note:** Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications
2016-08-10 05:15:44 +00:00
"es6-promise": "^3.2.1",
Testing/linting setup (#120)
2016-09-06 18:41:16 +00:00
"expect": "^1.20.2",
React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. **Note:** Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications
2016-08-10 05:15:44 +00:00
"expose-loader": "^0.7.1",
"express": "^4.13.4",
"extract-text-webpack-plugin": "^1.0.1",
"file-loader": "^0.8.5",
"history": "2.0.0",
Login page form submission (#157) * API client utility * moves test helpers to the test directory * Utility to namespace local storage keys * LoginSuccessfulPage component * Check icon * adds auth to redux state * successful form submission * Allow tests to load dummy SVG static images & test fixes
2016-09-13 19:50:37 +00:00
"isomorphic-fetch": "^2.2.1",
Logout (#195) * moves login page styles to reusable component * Redirects successful login to homepage after 3s * Adds logout form * Adds logout page * Adds logout link to homepage * Adds gravatarURL to logged in user * Configure API Client to hit /me endpoint * Fetch user when the app loads * Configured API Client to make logout requests * Handle logout flow in redux * Logout form styles * Logout user when the logout form is submitted
2016-09-19 23:43:35 +00:00
"js-md5": "^0.4.1",
Testing/linting setup (#120)
2016-09-06 18:41:16 +00:00
"jsdom": "^9.5.0",
React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. **Note:** Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications
2016-08-10 05:15:44 +00:00
"lodash": "^4.3.0",
Login page form submission (#157) * API client utility * moves test helpers to the test directory * Utility to namespace local storage keys * LoginSuccessfulPage component * Check icon * adds auth to redux state * successful form submission * Allow tests to load dummy SVG static images & test fixes
2016-09-13 19:50:37 +00:00
"nock": "^8.0.0",
React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. **Note:** Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications
2016-08-10 05:15:44 +00:00
"postcss-functions": "^2.1.0",
"postcss-loader": "^0.8.0",
"precss": "^1.4.0",
"proxy-middleware": "^0.15.0",
Changes CSS styles to JS using Radium (#129)
2016-09-07 20:07:45 +00:00
"radium": "^0.18.1",
"radium-normalize": "^2.0.4",
React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. **Note:** Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications
2016-08-10 05:15:44 +00:00
"react": "^15.2.1",
"react-dom": "^15.2.1",
Redux configuration (#122)
2016-09-07 00:04:02 +00:00
"react-redux": "^4.4.5",
"react-router": "^2.7.0",
"react-router-redux": "^4.0.5",
"redux": "^3.6.0",
Login page form submission (#157) * API client utility * moves test helpers to the test directory * Utility to namespace local storage keys * LoginSuccessfulPage component * Check icon * adds auth to redux state * successful form submission * Allow tests to load dummy SVG static images & test fixes
2016-09-13 19:50:37 +00:00
"redux-mock-store": "^1.2.0",
Redux configuration (#122)
2016-09-07 00:04:02 +00:00
"redux-thunk": "^2.1.0",
Login page form submission (#157) * API client utility * moves test helpers to the test directory * Utility to namespace local storage keys * LoginSuccessfulPage component * Check icon * adds auth to redux state * successful form submission * Allow tests to load dummy SVG static images & test fixes
2016-09-13 19:50:37 +00:00
"require-hacker": "^2.1.4",
React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. **Note:** Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications
2016-08-10 05:15:44 +00:00
"style-loader": "^0.13.0",
"stylus-loader": "1.5.1",
Icon component setup & bg image (#133)
2016-09-08 12:50:44 +00:00
"url-loader": "^0.5.7",
React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. **Note:** Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications
2016-08-10 05:15:44 +00:00
"webpack": "1.13.1",
"webpack-dev-middleware": "^1.5.1",
"webpack-hot-middleware": "^2.7.1",
"whatwg-fetch": "^0.11.0",
"when": "^3.7.7"
},
"babel": {
"presets": [
"es2015",
"react",
"stage-0"
],
"env": {
"dev": {
"presets": [
"react-hmre"
]
}
}
},
Testing/linting setup (#120)
2016-09-06 18:41:16 +00:00
"devDependencies": {
"babel-eslint": "^6.1.2",
"eslint": "^3.4.0",
"eslint-config-airbnb": "^10.0.1",
"eslint-plugin-import": "^1.14.0",
"eslint-plugin-jsx-a11y": "^2.1.1",
"eslint-plugin-react": "^6.0.0",
"mocha": "^3.0.2",
"react-addons-test-utils": "^15.3.1",
"react-dom": "^15.3.1"
React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. **Note:** Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications
2016-08-10 05:15:44 +00:00
}
}
Reference in New Issue Copy Permalink