Skip to content

Commit cae4477

Browse files
authored
Update contributing.md
1 parent b40efb3 commit cae4477

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

packages/gatsby/content/advanced/contributing.md

+3-5
Original file line numberDiff line numberDiff line change
@@ -30,14 +30,12 @@ It might be difficult to know where to start on a fresh codebase. To help a bit
3030

3131
Finally, feel free to pop on our [Discord channel](https://discordapp.com/invite/yarnpkg) to ask for help and guidance. We're always happy to see new blood, and will help you our best to make your first open-source contribution a success!
3232

33-
## Working on plugins
33+
## Writing your feature
3434

35-
The standard bundle uses a predefined set of plugins defined in [`packages/yarnpkg-cli/package.json`](https://github.com/yarnpkg/berry/blob/master/packages/yarnpkg-cli/package.json#L64). If your PR aims to add a new plugin to the standard build you'll need to add it there (note that this decision should be left to the core maintainers - please don't modify this setting yourself).
36-
37-
For development purposes, you can build your plugin as part of your own local bundle by using the `--plugin` option in the command line:
35+
Our repository is setup in such a way that calling `yarn` inside it will always use the TypeScript sources themselves - you don't have to rebuild anything for your changes to be applied there (we use `@babel/register` to automatically transpile the files as we require them). The downside is that it's slower than the regular Yarn, but the improved developer experience is well worth it.
3836

3937
```bash
40-
yarn build:cli --plugin @yarnpkg/plugin-typescript
38+
yarn install # Will automatically pick up any changes you made to sources
4139
```
4240

4341
## Testing your code

0 commit comments

Comments
 (0)