Update name and package info

Author: Alireza Zamani

README.md

@@ -14,21 +14,21 @@ To use pagination in GraphQL, it's proposed by the spec that we use the "Connect
 On Yarn:
 
 ```shell
-yarn add @exonest/graphql-connections
+yarn add nestjs-gql-connections
 ```
 
 On NPM:
 
 ```shell
-npm install @exonest/graphql-connections
+npm install nestjs-gql-connections
 ```
 
 ## Usage
 
 You can create a new paginated model like so:
 
 ```ts
-import { Paginated } from '@exonest/graphql-connections';
+import { Paginated } from 'nestjs-gql-connections';
 import { Product } from '../product.model';
 
 export class ProductConnection extends Paginated(Product) {}
@@ -49,7 +49,7 @@ resourcePublications(
 
 ## Apollo Cache Compatability
 
-Be default, Apollo server won't cache if a field on resolver is an object (non-scalar), thinking non-scalar fields need fetching and are probably somehow independent ([more info](https://www.apollographql.com/docs/apollo-server/performance/caching/#default-maxage)). While in the case of pagination's `node` object or `edges`, they are already fetched and available. So we've added cache control inheritance to all the respective fields and you don't really have to worry about that. This package goes nicely with the other exonest package for GraphQL caching, [exonest/graphql-cache-control](https://github.com/exonest/graphql-cache-control)
+Be default, Apollo server won't cache if a field on resolver is an object (non-scalar), thinking non-scalar fields need fetching and are probably somehow independent ([more info](https://www.apollographql.com/docs/apollo-server/performance/caching/#default-maxage)). While in the case of pagination's `node` object or `edges`, they are already fetched and available. So we've added cache control inheritance to all the respective fields and you don't really have to worry about that. This package goes nicely with the other [overnested](https://github.com/overnested) package for GraphQL caching, [overnested/graphql-cache-control](https://github.com/overnested/graphql-cache-control)
 
 ## With Prisma
 

package.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.1.0",
+  "version": "0.1.1",
   "license": "MIT",
   "main": "dist/index.js",
   "typings": "dist/index.d.ts",
@@ -10,10 +10,10 @@
   "engines": {
     "node": ">=10"
   },
-  "homepage": "https://github.com/exonest",
+  "homepage": "https://github.com/overnested",
   "repository": {
     "type": "git",
-    "url": "https://github.com/exonest/graphql-connections"
+    "url": "https://github.com/overnested/nestjs-gql-connections"
   },
   "scripts": {
     "start": "tsdx watch",
@@ -36,16 +36,16 @@
     "singleQuote": true,
     "trailingComma": "es5"
   },
-  "name": "@exonest/graphql-connections",
+  "name": "@overnested/nestjs-gql-connections",
   "author": "Alireza Zamani",
-  "module": "dist/graphql-connections.esm.js",
+  "module": "dist/nestjs-gql-connections.esm.js",
   "size-limit": [
     {
-      "path": "dist/graphql-connections.cjs.production.min.js",
+      "path": "dist/nestjs-gql-connections.cjs.production.min.js",
       "limit": "10 KB"
     },
     {
-      "path": "dist/graphql-connections.esm.js",
+      "path": "dist/nestjs-gql-connections.esm.js",
       "limit": "10 KB"
     }
   ],