Discussion: TRL 0.2.0-next.1 Pre-release
Greets @FVTT ▹ Developer,
I'd like to open a discussion prior to the initial
The discussion below relates to
---
Repo and NPM package name changes.
The main repo in typhonjs-fvtt-lib is now
I will be making a new NPM package release for the standard library:
---
This release is large and will require some package import refactoring depending on what parts of TRL you utilize in your projects. Please see the pre-release 0.2.0 API docs which have now been updated reflecting all of the sub-path changes.
More or less a lot of these changes affect the standard component library as now instead of
The following changes will be the most likely:
- All application shell components
-
- Components from the standard library will now have more explicit groups / sub-paths. Expand the tree for
I was able to make tremendous progress in the last week cleanly separating all non-Foundry specific components from the FVTT standard library into a base standard component library that can be used anywhere. This significantly increases the timeline of the Svelte 5 transition because I can now iterate on the Svelte 5 conversion without involving Foundry itself.
To facilitate this separation though the Vite config will need a small mod:
Adding the
---
There is only one code / breaking change. In the past various callbacks whether for app header buttons, TJSDialog callbacks, or various components from the standard library that provide data defined callbacks took argument lists. Instead of a variable number of arguments a single
If you have a dialog callback for instance that previously was:
all you have to do is add
That's the breaking change for
I'd like to open a discussion prior to the initial
0.2.0-next.1next.Xv12The discussion below relates to
0.2.00.1.x---
Repo and NPM package name changes.
The main repo in typhonjs-fvtt-lib is now
runtimetyphonjssvelte-standardstandardI will be making a new NPM package release for the standard library:
@typhonjs-fvtt/standardsvelte-standard---
This release is large and will require some package import refactoring depending on what parts of TRL you utilize in your projects. Please see the pre-release 0.2.0 API docs which have now been updated reflecting all of the sub-path changes.
More or less a lot of these changes affect the standard component library as now instead of
#standard/component#standard/component/buttonThe following changes will be the most likely:
- All application shell components
#runtime/svelte/component/core#runtime/svelte/component/application-
localize#runtime/svelte/helper#runtime/util/i18n- Components from the standard library will now have more explicit groups / sub-paths. Expand the tree for
#standard/componentsI was able to make tremendous progress in the last week cleanly separating all non-Foundry specific components from the FVTT standard library into a base standard component library that can be used anywhere. This significantly increases the timeline of the Svelte 5 transition because I can now iterate on the Svelte 5 conversion without involving Foundry itself.
To facilitate this separation though the Vite config will need a small mod:
Adding the
alias---
There is only one code / breaking change. In the past various callbacks whether for app header buttons, TJSDialog callbacks, or various components from the standard library that provide data defined callbacks took argument lists. Instead of a variable number of arguments a single
objectIf you have a dialog callback for instance that previously was:
all you have to do is add
{}That's the breaking change for
0.2.0