@graphcommerce/docs 4.6.4 → 4.6.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # Change Log
2
2
 
3
+ ## 4.6.5
4
+
5
+ ### Patch Changes
6
+
7
+ - [#1584](https://github.com/graphcommerce-org/graphcommerce/pull/1584) [`f424f3da1`](https://github.com/graphcommerce-org/graphcommerce/commit/f424f3da125d2ec961ae60ebec7a65825710f72c) Thanks [@paales](https://github.com/paales)! - fixed typo from grapql to graphql
8
+
3
9
  ## 4.6.4
4
10
 
5
11
  ### Patch Changes
@@ -47,7 +47,7 @@ If you want to test a GraphCommerce storefront using a pre-configured Magento
47
47
  demo store and a pre-configured GraphCMS project with demo content, then you
48
48
  need to only install the dependencies. This is the quickest approach.
49
49
 
50
- - Install and use node 14: `nvm install 14 && nvm use 14`
50
+ - Install and use node 14: `nvm install 14` or `nvm use 14`
51
51
  - Install yarn: `npm install --global yarn`
52
52
 
53
53
  ## Step 1: Create a new GraphCommerce app
@@ -65,13 +65,12 @@ https://user-images.githubusercontent.com/1251986/158647122-dc57002f-a9c2-4661-a
65
65
 
66
66
  ### Download the example
67
67
 
68
- 1. `git clone git@github.com:graphcommerce-org/graphcommerce.git`
69
- 2. `mkdir my-project`
70
- 3. `cp -R graphcommerce/examples/magento-graphcms/. my-project && rm -rf graphcommerce`
71
- 4. `cd my-project`
72
- 5. `cp -R .env.example .env`
73
- 6. `rm CHANGELOG.md`
74
- 7. `rm -rf node_modules && rm -rf .next`
68
+ 1. `git clone https://github.com/graphcommerce-org/graphcommerce.git` — clone repository
69
+ 2. `mkdir my-project` — create project folder
70
+ 3. `cp -R graphcommerce/examples/magento-graphcms/. my-project && rm -rf graphcommerce` — copy example, delete repo
71
+ 4. `cd my-project` — change directory to project folder
72
+ 5. `cp -R .env.example .env` — create .env file
73
+ 6. `rm CHANGELOG.md` — remove changelog
75
74
 
76
75
  Edit /package.json. Delete `"scripts": {...}` and rename `scripts_local` to
77
76
  `scripts`:
@@ -211,7 +211,7 @@ API. GraphCommerce uses GraphQL Mesh, which adds the ability to add extra
211
211
  (micro)services as data sources. In the magento-graphcms example, a headless CMS
212
212
  called [GraphCMS](../getting-started/../framework/graphcms.md) is integrated.
213
213
 
214
- By default, the GraphQL Mesh endpoint runs on route /api/grapql. You can query
214
+ By default, the GraphQL Mesh endpoint runs on route /api/graphql. You can query
215
215
  both the Magento GraphQL schema and the GraphCMS GraphQL schema. Try out the
216
216
  GraphCommerce demo
217
217
  [GraphQL Explorer ↗](https://graphcommerce.vercel.app/api/graphql) with the
package/package.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "name": "@graphcommerce/docs",
3
3
  "homepage": "https://www.graphcommerce.org/docs",
4
4
  "repository": "github:graphcommerce-org/graphcommerce/docs",
5
- "version": "4.6.4",
5
+ "version": "4.6.5",
6
6
  "sideEffects": true,
7
7
  "devDependencies": {
8
8
  "@graphcommerce/prettier-config-pwa": "^4.0.6"