feat(tokens): change prefix and update scripts to use modules logic #30663
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BenOsodrac
added
type: feature request
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number: internal
What is the new behavior?
This pull request updates the design token build pipeline to support ECMAScript modules and Style Dictionary v5, improves maintainability, and modernizes the codebase. The most important changes are grouped below:
Migration to ECMAScript Modules and Style Dictionary v5:
index.js) to ECMAScript modules (index.mjs), updating all imports/exports and adapting the code to Style Dictionary v5 format requirements. (core/scripts/tokens/index.jsremoved,core/scripts/tokens/index.mjsadded) [1] [2]package.jsonto use the newindex.mjsfile for thebuild.tokenscommand.style-dictionarydependency from v4 to v5 inpackage.jsonto support the new module format and features.Code Modernization and Refactoring:
utils.jstoutils.mjsand converted all utility functions to use ES module exports, improving future compatibility and maintainability. (core/scripts/tokens/utils.jsrenamed and refactored tocore/scripts/tokens/utils.mjs) [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]Design Token Package Update:
outsystems-design-tokensdependency from v1.3.0 to v1.3.2 inpackage.jsonto ensure compatibility with the latest token definitions.Does this introduce a breaking change?