fix: Fix type file generation to export types instead of declarations #120
Conversation
This file contains 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
RayRedGoose
commented
Jul 3, 2024
RayRedGoose
commented
Jul 3, 2024
NicholasBoll
approved these changes
Jul 3, 2024
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
Fixes #119
Summary
PR contains a fix for type issue for users don't use
--skipLibCheck.Release Category
Web Tokens
Release Note
Type generation has been updated to fix a type issue happening for user who doesn't use
--skipLibCheck. Now generated type files contains types (export declare const cinnamon100: "--cnvs-base-palette-cinnamon-100";) instead of value declarations (export declare const cinnamon100 = "--cnvs-base-palette-cinnamon-100" as const;).