Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v2.0 - React v18 support #144

Open
palerdot opened this issue Apr 10, 2022 · 3 comments
Open

v2.0 - React v18 support #144

palerdot opened this issue Apr 10, 2022 · 3 comments

Comments

@palerdot
Copy link
Owner

palerdot commented Apr 10, 2022

v2.0 with React v18 support is in RC and available as next tag. You can install it with

npm install react-d3-speedometer@next

This PR has support for v18 React - #143. The changes will be published as a major version of the package v2.0. Along with this upgrade, some notable changes to the package are

  • Slim Build: Starting from v2.0, a slim build of the package will be available without bundling d3 related modules. If you are already using d3 (prefarably via d3 microbundles like d3-selection etc), you can take advantage of the slim build.
  • Vite: Switching to vite for dev/prod building
  • Vitest: Switching to vitest for testing
  • Cypress/RTL: For testing, this package will be moving away from enzyme. For more context, please check https://dev.to/wojtekmaj/enzyme-is-dead-now-what-ekl
  • Exporting es, umd builds. The package will now both export es compatible build and umd compatible build by default. Library users are encouraged to make use of es build for better tree shaking in their app. Please note, slim build will not be available as a umd build. Also, the package has switched to d3 micromodules (eg: d3-ease, d3-transition etc) for better tree shaking.
@palerdot palerdot pinned this issue Apr 10, 2022
@hect1c
Copy link

hect1c commented Apr 17, 2022

Hey @palerdot Thanks for the package first of all

I just upgraded to v18 react and can confirm I was having issues with react-d3-speedometer. Luckily I found this issue where you are already on top of it and using the @next has solved the issue I had. My error was

TypeError: b.pointer.transition is not a function

Great job, thanks!

@palerdot
Copy link
Owner Author

Hey @hect1c

Good to know. In case you face any troubles with v2.0/ v18 React, please raise an issue.

Repository owner deleted a comment from IsAmitprajapati Jul 12, 2022
Repository owner locked as resolved and limited conversation to collaborators Jul 12, 2022
@palerdot
Copy link
Owner Author

PS: I'm locking this issue to avoid people posting their issues as comment. Please open a new issue if you are facing any problem. This issue is for information/announcement purposes only.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants