1- ### Getting Started
1+ # Getting Started
22
33Please note that we require a signed GraphQL Specification Membership agreement
44before landing a contribution. This is checked automatically when you open a PR.
@@ -9,8 +9,9 @@ prompted by the EasyCLA bot. For more details, please see the
990 . First, you will need the latest ` git ` , ` yarn ` 1.16, & ` node ` 12 or greater.
1010 macOS, Windows and Linux should all be supported as build environments.
1111
12- _ ** Note:** None of the commands below will work with ` npm ` . Please use ` yarn ` in
13- this repo._
12+ > [ !WARNING]
13+ >
14+ > None of the commands below will work with ` npm ` . Please use ` yarn ` in this repo.
1415
15161 . Fork this repo by using the "Fork" button in the upper-right
1617
@@ -29,35 +30,35 @@ this repo._
29304 . Build all interdependencies so the project you are working on can resolve
3031 other packages
3132
32- First you'll need —
33+ First, you'll need:
3334
3435 ``` sh
3536 yarn build
3637 ```
3738
38- — or —
39+ or
3940
4041 ``` sh
4142 yarn build:watch
4243 ```
4344
44- If you are focused on GraphiQL development, you can run —
45+ If you are focused on GraphiQL development, you can run:
4546
4647 ``` sh
47- yarn dev- graphiql
48+ yarn dev: graphiql
4849 ```
4950
50515 . Get coding! If you've added code, add tests. If you've changed APIs, update
5152 any relevant documentation or tests. Ensure your work is committed within a
5253 feature branch.
5354
54- 6 . Ensure all tests pass, and build everything
55+ 6 . Ensure all tests pass and build everything
5556
5657 ``` sh
5758 yarn test
5859 ```
5960
60- ### Fix CI issues with linting
61+ ## Fix CI issues with linting
6162
6263If you have ` prettier ` or ` eslint --fix ` -able issues you see in CI, use —
6364
@@ -67,7 +68,7 @@ If you see `typescript` build issues, do a `yarn build` locally, and make sure
6768the whole project references tree builds. Changing interfaces can end up
6869breaking their implementations.
6970
70- ### Run tests for GraphiQL:
71+ ## Run tests for GraphiQL:
7172
7273- ` yarn test graphiql ` will run all tests for graphiql. You can also run tests
7374 from a workspace, but most tooling is at the root.
@@ -80,28 +81,30 @@ breaking their implementations.
8081If you want these commands to watch for changes to dependent packages in the
8182repo, then run ` yarn build --watch ` alongside either of these.
8283
83- ### Developing for GraphiQL
84+ ## Developing for GraphiQL
8485
8586If you want to develop just for graphiql, you won't need to execute commands
8687from the package subdirectory at ` packages/graphiql ` .
8788
8889First, you'll need to ` yarn build ` all the packages from the root.
8990
90- Then, you can run these commands:
91+ Then, you can run ` yarn dev:graphiql ` command, which will launch ` vite ` dev server for GraphiQL.
9192
92- - ` yarn dev-graphiql ` — which will launch ` webpack ` dev server for graphiql
93- from the root
93+ ``` text
94+ VITE v6.3.4 ready in 1015 ms
9495
95- > The GraphiQL UI is available at http://localhost:8080/dev.html
96+ ➜ Local: http://localhost:5173/
97+ ➜ Network: use --host to expose
98+ ```
9699
97- ### Developing Monaco GraphQL
100+ ## Developing Monaco GraphQL
98101
991021 . First run ` yarn ` .
100- 2 . run ` yarn tsc --watch ` to watch ` monaco-graphql ` and
103+ 2 . Run ` yarn tsc --watch ` to watch ` monaco-graphql ` and
101104 ` graphql-language-service ` in one screen session/terminal tab/etc
102- 3 . in another session, run ` yarn start-monaco ` from anywhere in the repository
105+ 3 . In another session, run ` yarn start-monaco ` from anywhere in the repository
103106 aside from an individual workspace.
104- 4 . alternatively to the webpack example, or in addition, you can run monaco or
107+ 4 . Alternatively to the webpack example, or in addition, you can run monaco or
105108 next.js examples, though these examples are simpler. They also require their
106109 own ` yarn ` or ` npm install ` as they are excluded from the ` workspaces `
107110 resolved on global ` yarn install `
0 commit comments