Conversation
0f9ef8d to
5f01c98
Compare
418107b to
b1f0605
Compare
sBouzols
reviewed
Apr 9, 2026
sBouzols
reviewed
Apr 9, 2026
sBouzols
reviewed
Apr 9, 2026
34e8c30 to
0860fe3
Compare
|
chore: - update dev dependencies across packages - Refactored tests in svg-utils.test.ts for improved style formatting. - Added ESLint disable comments in network-map.tsx to prevent warnings related to state updates in effects. - Update license header year 2025 -> 2026 on new files Signed-off-by: Arnaud Marant <arnaud.marant@rte-france.com>
|
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.



Vite is not a tool optimized for building librairies, it makes us create big, complex and fragile vite.config where we list all dependencies, invoque the dts plugin manually. Tsdown is the preferred tool for that and from the same team with the same maturity.
Here we move from vite to tsdown for all 3 libs, and keep vite for the demo.
We also add publint check to validate the lib builds.
chore: update dev dependencies across packages
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
What kind of change does this PR introduce?
Build tool changes.
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?