artemis-client
Advanced tools
Comparing version 0.2.0 to 1.0.0
106
package.json
{ | ||
"name": "artemis-client", | ||
"version": "0.2.0", | ||
"description": "Apollo's light-weight GraphQL client", | ||
"repository": { | ||
"type": "git", | ||
"url": "git+https://github.com/monojack/artemis-client.git" | ||
}, | ||
"keywords": [ | ||
"javascript", | ||
"apollo-client", | ||
"artemis-client", | ||
"graphql" | ||
"version": "1.0.0", | ||
"license": "MIT", | ||
"main": "dist/index.js", | ||
"typings": "dist/index.d.ts", | ||
"files": [ | ||
"dist", | ||
"src" | ||
], | ||
"author": "Ionut Achim <achimvionut@gmail.com>", | ||
"main": "./lib/index.js", | ||
"module": "es/index.js", | ||
"jsnext:main": "es/index.js", | ||
"dependencies": { | ||
"apollo-link": "1.0.6", | ||
"artemis-utilities": "0.1.5" | ||
"engines": { | ||
"node": ">=10" | ||
}, | ||
"devDependencies": { | ||
"babel-cli": "6.26.0", | ||
"babel-eslint": "8.0.3", | ||
"babel-plugin-external-helpers": "6.22.0", | ||
"babel-plugin-transform-es2015-modules-commonjs": "6.26.0", | ||
"babel-plugin-transform-object-rest-spread": "6.26.0", | ||
"babel-preset-env": "1.6.1", | ||
"babel-preset-es2015": "6.24.1", | ||
"babel-preset-stage-0": "6.24.1", | ||
"cross-env": "5.1.1", | ||
"eslint": "4.13.0", | ||
"eslint-config-standard": "10.2.1", | ||
"eslint-plugin-import": "2.8.0", | ||
"eslint-plugin-node": "5.2.1", | ||
"eslint-plugin-promise": "3.6.0", | ||
"eslint-plugin-standard": "3.0.1", | ||
"rimraf": "2.6.2", | ||
"rollup": "0.52.1", | ||
"rollup-analyzer-plugin": "1.1.1", | ||
"rollup-plugin-babel": "3.0.2", | ||
"rollup-plugin-commonjs": "8.2.6", | ||
"rollup-plugin-node-builtins": "2.1.2", | ||
"rollup-plugin-node-resolve": "3.0.0", | ||
"rollup-plugin-replace": "2.0.0", | ||
"rollup-plugin-uglify": "2.0.1" | ||
"scripts": { | ||
"start": "tsdx watch", | ||
"build": "tsdx build", | ||
"test": "tsdx test --passWithNoTests", | ||
"lint": "tsdx lint", | ||
"prepare": "tsdx build" | ||
}, | ||
"license": "MIT", | ||
"bugs": { | ||
"url": "https://github.com/monojack/artemis-client/issues" | ||
}, | ||
"peerDependencies": { | ||
"graphql": "^0.11.7" | ||
"react": ">=16" | ||
}, | ||
"scripts": { | ||
"build:cjs": "cross-env BABEL_ENV=cjs babel src --out-dir lib", | ||
"build:es": "cross-env BABEL_ENV=es babel src --out-dir es", | ||
"build:umd": "cross-env BABEL_ENV=rollup NODE_ENV=development rollup -c -o dist/artemis-client.js", | ||
"build:umd:min": "cross-env BABEL_ENV=rollup NODE_ENV=production rollup -c -o dist/artemis-client.min.js", | ||
"build": "npm run build:cjs && npm run build:es && npm run build:umd && npm run build:umd:min", | ||
"prepare": "npm run clean && npm run build", | ||
"lint": "eslint src", | ||
"clean": "rimraf lib dist es", | ||
"dev": "npm run build:es -- -w" | ||
"husky": { | ||
"hooks": { | ||
"pre-commit": "tsdx lint" | ||
} | ||
}, | ||
"npmName": "artemis-client", | ||
"files": [ | ||
"dist", | ||
"lib", | ||
"es" | ||
] | ||
"prettier": { | ||
"printWidth": 80, | ||
"semi": false, | ||
"singleQuote": true, | ||
"trailingComma": "es5" | ||
}, | ||
"name": "artemis-client", | ||
"description": "Artemis is an experimental hooks library that mirrors v3 of Apollo Client api", | ||
"author": "Francis Gulotta", | ||
"module": "dist/artemis-client.esm.js", | ||
"devDependencies": { | ||
"@types/jest": "^25.2.1", | ||
"@types/react": "^16.9.32", | ||
"@types/react-dom": "^16.9.6", | ||
"husky": "^4.2.3", | ||
"react": "^16.13.1", | ||
"react-dom": "^16.13.1", | ||
"tsdx": "^0.13.1", | ||
"tslib": "^1.11.1", | ||
"typescript": "^3.8.3" | ||
} | ||
} |
210
README.md
@@ -1,3 +0,209 @@ | ||
# Artemis | ||
# Artemis Client | ||
[Apollo](https://github.com/apollographql/apollo-client)'s light-weight GraphQL client. | ||
Artemis is an experimental hooks library that mirrors [v3 of Apollo Client api](https://www.apollographql.com/docs/react/v3.0-beta/data/queries/) for use with RESTish apis. The idea is to provide a common api pattern for accessing all apis graphql and REST. | ||
A [Justworks](https://grnh.se/ade4dbf91) sponsored project. | ||
## API | ||
### Query Interface | ||
Sometimes you want to GET data right away. | ||
```jsx | ||
import React from 'react'; | ||
import { useQuery } from 'artemis-client'; | ||
const CatPhoto = ({ breed }) => { | ||
const { loading, error, data, refetch } = useQuery(CAT_PHOTO_PATH, { | ||
variables: { breed }, | ||
skip: !breed, | ||
}); | ||
if (loading) return `Loading`; | ||
if (error) return `Error! ${error.message}`; | ||
return ( | ||
<div> | ||
<img src={data.cat.displayImage} style={{ height: 100, width: 100 }} /> | ||
<button onClick={() => refetch()}>Refetch!</button> | ||
</div> | ||
); | ||
} | ||
``` | ||
## TODO | ||
- Testing approach | ||
- Lazy Query | ||
- Mutation | ||
## TSDX | ||
This project uses TSDX which is pretty rad, it's readme is below. | ||
Congrats! You just saved yourself hours of work by bootstrapping this project with TSDX. Let’s get you oriented with what’s here and how to use it. | ||
> This TSDX setup is meant for developing React components (not apps!) that can be published to NPM. If you’re looking to build an app, you should use `create-react-app`, `razzle`, `nextjs`, `gatsby`, or `react-static`. | ||
> If you’re new to TypeScript and React, checkout [this handy cheatsheet](https://github.com/sw-yx/react-typescript-cheatsheet/) | ||
## Commands | ||
TSDX scaffolds your new library inside `/src`, and also sets up a [Parcel-based](https://parceljs.org) playground for it inside `/example`. | ||
The recommended workflow is to run TSDX in one terminal: | ||
```bash | ||
npm start # or yarn start | ||
``` | ||
This builds to `/dist` and runs the project in watch mode so any edits you save inside `src` causes a rebuild to `/dist`. | ||
Then run the example inside another: | ||
```bash | ||
cd example | ||
npm i # or yarn to install dependencies | ||
npm start # or yarn start | ||
``` | ||
The default example imports and live reloads whatever is in `/dist`, so if you are seeing an out of date component, make sure TSDX is running in watch mode like we recommend above. **No symlinking required**, [we use Parcel's aliasing](https://github.com/palmerhq/tsdx/pull/88/files). | ||
To do a one-off build, use `npm run build` or `yarn build`. | ||
To run tests, use `npm test` or `yarn test`. | ||
## Configuration | ||
Code quality is [set up for you](https://github.com/palmerhq/tsdx/pull/45/files) with `prettier`, `husky`, and `lint-staged`. Adjust the respective fields in `package.json` accordingly. | ||
### Jest | ||
Jest tests are set up to run with `npm test` or `yarn test`. This runs the test watcher (Jest) in an interactive mode. By default, runs tests related to files changed since the last commit. | ||
#### Setup Files | ||
This is the folder structure we set up for you: | ||
```shell | ||
/example | ||
index.html | ||
index.tsx # test your component here in a demo app | ||
package.json | ||
tsconfig.json | ||
/src | ||
index.tsx # EDIT THIS | ||
/test | ||
blah.test.tsx # EDIT THIS | ||
.gitignore | ||
package.json | ||
README.md # EDIT THIS | ||
tsconfig.json | ||
``` | ||
#### React Testing Library | ||
We do not set up `react-testing-library` for you yet, we welcome contributions and documentation on this. | ||
### Rollup | ||
TSDX uses [Rollup v1.x](https://rollupjs.org) as a bundler and generates multiple rollup configs for various module formats and build settings. See [Optimizations](#optimizations) for details. | ||
### TypeScript | ||
`tsconfig.json` is set up to interpret `dom` and `esnext` types, as well as `react` for `jsx`. Adjust according to your needs. | ||
## Continuous Integration | ||
### Travis | ||
_to be completed_ | ||
### Circle | ||
_to be completed_ | ||
## Optimizations | ||
Please see the main `tsdx` [optimizations docs](https://github.com/palmerhq/tsdx#optimizations). In particular, know that you can take advantage of development-only optimizations: | ||
```js | ||
// ./types/index.d.ts | ||
declare var __DEV__: boolean; | ||
// inside your code... | ||
if (__DEV__) { | ||
console.log('foo'); | ||
} | ||
``` | ||
You can also choose to install and use [invariant](https://github.com/palmerhq/tsdx#invariant) and [warning](https://github.com/palmerhq/tsdx#warning) functions. | ||
## Module Formats | ||
CJS, ESModules, and UMD module formats are supported. | ||
The appropriate paths are configured in `package.json` and `dist/index.js` accordingly. Please report if any issues are found. | ||
## Using the Playground | ||
```bash | ||
cd example | ||
npm i # or yarn to install dependencies | ||
npm start # or yarn start | ||
``` | ||
The default example imports and live reloads whatever is in `/dist`, so if you are seeing an out of date component, make sure TSDX is running in watch mode like we recommend above. **No symlinking required**! | ||
## Deploying the Playground | ||
The Playground is just a simple [Parcel](https://parceljs.org) app, you can deploy it anywhere you would normally deploy that. Here are some guidelines for **manually** deploying with the Netlify CLI (`npm i -g netlify-cli`): | ||
```bash | ||
cd example # if not already in the example folder | ||
npm run build # builds to dist | ||
netlify deploy # deploy the dist folder | ||
``` | ||
Alternatively, if you already have a git repo connected, you can set up continuous deployment with Netlify: | ||
```bash | ||
netlify init | ||
# build command: yarn build && cd example && yarn && yarn build | ||
# directory to deploy: example/dist | ||
# pick yes for netlify.toml | ||
``` | ||
## Named Exports | ||
Per Palmer Group guidelines, [always use named exports.](https://github.com/palmerhq/typescript#exports) Code split inside your React app instead of your React library. | ||
## Including Styles | ||
There are many ways to ship styles, including with CSS-in-JS. TSDX has no opinion on this, configure how you like. | ||
For vanilla CSS, you can include it at the root directory and add it to the `files` section in your `package.json`, so that it can be imported separately by your users and run through their bundler's loader. | ||
## Publishing to NPM | ||
We recommend using [np](https://github.com/sindresorhus/np). | ||
## Usage with Lerna | ||
When creating a new package with TSDX within a project set up with Lerna, you might encounter a `Cannot resolve dependency` error when trying to run the `example` project. To fix that you will need to make changes to the `package.json` file _inside the `example` directory_. | ||
The problem is that due to the nature of how dependencies are installed in Lerna projects, the aliases in the example project's `package.json` might not point to the right place, as those dependencies might have been installed in the root of your Lerna project. | ||
Change the `alias` to point to where those packages are actually installed. This depends on the directory structure of your Lerna project, so the actual path might be different from the diff below. | ||
```diff | ||
"alias": { | ||
- "react": "../node_modules/react", | ||
- "react-dom": "../node_modules/react-dom" | ||
+ "react": "../../../node_modules/react", | ||
+ "react-dom": "../../../node_modules/react-dom" | ||
}, | ||
``` | ||
An alternative to fixing this problem would be to remove aliases altogether and define the dependencies referenced as aliases as dev dependencies instead. [However, that might cause other problems.](https://github.com/palmerhq/tsdx/issues/64) |
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
Network access
Supply chain riskThis module accesses the network.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 1 instance in 1 package
Minified code
QualityThis package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code.
Found 1 instance in 1 package
No bug tracker
MaintenancePackage does not have a linked bug tracker in package.json.
Found 1 instance in 1 package
No repository
Supply chain riskPackage does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Minified code
QualityThis package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
1
9
2
210
28009
12
285
1
2
5
+ Addedjs-tokens@4.0.0(transitive)
+ Addedloose-envify@1.4.0(transitive)
+ Addedreact@18.3.1(transitive)
- Removedapollo-link@1.0.6
- Removedartemis-utilities@0.1.5
- Removed@types/zen-observable@0.5.3(transitive)
- Removed@wry/equality@0.1.11(transitive)
- Removedapollo-link@1.0.6(transitive)
- Removedapollo-utilities@1.3.4(transitive)
- Removedartemis-utilities@0.1.5(transitive)
- Removedfast-json-stable-stringify@2.1.0(transitive)
- Removedgraphql@0.11.7(transitive)
- Removediterall@1.1.3(transitive)
- Removedts-invariant@0.4.4(transitive)
- Removedtslib@1.14.1(transitive)
- Removedzen-observable@0.6.1(transitive)