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
The default generation scripts should include TypeScript es6 definition files as well. It does not interfere with JS modules and improves TypeScript support:
# Pull Request
## 🤨 Rationale
Added a workaround that avoids forking the DSP generated config.js and enables TypeScript Type Definitions for the JS Build. Could remove after: AdobeXD/design-system-package-dsp#22
## 👩💻 Implementation
Specified a custom config file in the DSP configuration. The custom file loads the one generated by the design system and patches it for the TypeScript configuration changes.
I noticed that even with a custom file specified the DSP plugin will still assume the original config.js exists and will always create or update it. The extend and patch workflow in `nimble-config.js` should allow us to leverage the GUI config for the DSP to generate a `config.js` and patch it for custom behavior in `nimble-config.js`.
## 🧪 Testing
Tested with the XD extension locally.
## ✅ Checklist
- [X] I have updated the project documentation to reflect my changes. Don't think any updates needed.
The JS build only emits a JS file based on the following configuration generated by the DSP:
The default generation scripts should include TypeScript es6 definition files as well. It does not interfere with JS modules and improves TypeScript support:
The text was updated successfully, but these errors were encountered: