You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We also have a number of documentation-specific helper components that can be imported and used where necessary. For these shared components, if you are using both `CodeBlock` and `Disclosure` on the same page, you can import them both like so:
For more information about importing things in Javascript, please refer to [import on MDN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import).
3. After you're done with your changes and have tested that all is well, feel free to make a pull request and it will get reviewed, and hopefully merged into the source code. The version will get bumped and all the sites will have to make an update to their dependencies as well.
63
+
64
+
## Local development
65
+
66
+
All commands are run from the root of the project, from a terminal:
|`npm run format`| Format code and fix linting issues |
72
+
|`npm run lint`| Check code formatting and linting |
73
+
74
+
You can substitute the `npm` commands with whatever package manager your workflow uses.
75
+
76
+
### 🔍 Code Formatting
77
+
78
+
This project uses [ESLint](https://eslint.org/) for code linting and [Prettier](https://prettier.io/) for code formatting. Before submitting a pull request, please ensure your code is properly formatted:
79
+
80
+
1.**Fix issues**: Run `npm run format` to automatically format code and fix linting issues.
81
+
2.**Check before pushing**: Run `npm run lint` to verify everything passes (CI will also run this).
82
+
83
+
ESLint is configured to work with TypeScript and Astro files. The configuration extends recommended rules from ESLint, TypeScript ESLint, and Astro ESLint plugins, and integrates with Prettier to avoid conflicts.
0 commit comments