Merged
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@tabula/forge@2.0.0
Major Changes
#57
d3c40d7Thanks @demiazz! - enablememoby default for SVGR transformations#60
5611eadThanks @demiazz! - update target node up to 20.xMinor Changes
#62
bcd685aThanks @demiazz! - emulate Vite's environment variablesThe
vanilla-extractusesesbuildunder the hood with CJS format. In that case, if you import any code with usage ofimport.We assume usage only
import.meta.env.DEV,import.meta.env.PRODandimport.meta.env.MODEvariables in bundleruser's code and emulate only it with defining constants.
But this constants working only in compile time when CSS is generated and based on mode in which the
forgeis runningat compilation moment.
Be careful when use code which based on that variables in your
vanilla-extractstyles.#57
d3c40d7Thanks @demiazz! - added support of transformation of SVG component name withsvgrComponentNameoption.By default, SVGR uses
Svg<CamelCaseFileName>name for components. You can override this behaviour throughsvgrComponentNameoptions, which should be function of format(svgrName: string) => string.Example:
If you have a file
column.svgthen component name isSvgColumnby default. But with config from about the namewill be
UiColumnIcon.If you use memoization it looks like:
This option doesn't affect named exports.
#57
d3c40d7Thanks @demiazz! - allow to appenddisplayNamefor SVGR components.By default, SVGR doesn't append
displayNamefor exported components. You can add this behaviour throughsvgrDisplayNameoption, which should be function of format
(componentName: string) => string | { displayName: string; isDebugOnly?: boolean }.When function is returns string, then
isDebugOnlyequals tofalse.The
componentNameis name of component itself (before memoization if enabled). If you providesvgrComponentNameoption,then result of applying this function is
componentName.The
isDebugOnlyenables wrapping the assignment in Vite compatible condition.If memoization is enabled, then the
displayNamewill be assigned to the memoized component:Patch Changes
#57
d3c40d7Thanks @demiazz! - add typings and exports config type#57
d3c40d7Thanks @demiazz! - add@babel/typesdependency