-
Notifications
You must be signed in to change notification settings - Fork 89
Tips and Tricks
-
For speedier CI test troubleshooting, you can update the
includeprop under thetestobject invite.config.tsto only run a specific suite (see example).test: { include: ["**/<component-to-focus-tests-on>.{e2e,spec}.?(c|m)[jt]s?(x)"], }
Just remember to restore it to its previous state after troubleshooting and before merging. 😅
-
You can use Chromatic's permalinks to directly share your Storybook builds for wider testing.
-
To be able to use
npm linkour packages with vite builds, make sure to add the following tovite.config.ts:optimizeDeps: { exclude: ["@esri/calcite-components"] }
see https://dev.to/hontas/using-vite-with-linked-dependencies-37n7
-
You can run tests within VS Code by using the preconfigured test runners (see https://github.com/Esri/calcite-design-system/blob/dev/.vscode/launch.json and https://code.visualstudio.com/docs/editor/debugging#_run-and-debug-view for more details).
- Monorepo
- Global Config
- Coding Conventions
- Testing Conventions
- Patching Packages
- Deprecation Guidance
- Continuous Integration
- GitHub Secrets
- Troubleshoot Build Errors
- Tips and Tricks
- NPM FAQ
- Issue Verification
- Wiki Conventions
- Styling Conventions
- CSS Transitions
- Restricting User Input
- ItemHidden Property
- What Happens When You Scale Vector-Based Icons
- Internationalization
- Introduction
- Getting Started
- Naming Schema
- Semantic Tokens
- Component Tokens
- Web Platform
- Build
- Documentation
- Testing
- Contributing