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

Chakra-ui/icon removed can't build project #267

Open
poseimus opened this issue Oct 30, 2024 · 4 comments
Open

Chakra-ui/icon removed can't build project #267

poseimus opened this issue Oct 30, 2024 · 4 comments

Comments

@poseimus
Copy link

poseimus commented Oct 30, 2024

when I try to build project the following error appears,

error during build: [vite]: Rollup failed to resolve import "@chakra-ui/icon" from "/Users/****/Desktop/****/****/node_modules/chakra-ui-steps/dist/chakra-ui-steps.es.js".

when I search a bit on web, chakra-ui/icon has been removed from chakra-ui so I think we need update for this to fix or any solution would be perfect I gotta get publish asap

I had build before with ^4.6.1 now can't

@masiulis
Copy link
Contributor

Hey @poseimus, does adding npm i @chakra-ui/icon to your project solve the issue?

@poseimus
Copy link
Author

poseimus commented Oct 30, 2024

Hey @poseimus, does adding npm i @chakra-ui/icon to your project solve the issue?

Hey had to import all of these

"@chakra-ui/icon": "^3.2.0",
"@chakra-ui/popper": "^3.1.0",
"@chakra-ui/react-context": "^2.1.0",
"@chakra-ui/system": "^2.6.2",

I got build but have to be sure about nothing breaks in react-spreadsheet-import usage :) lemme test

@poseimus
Copy link
Author

Seems ok with

"@chakra-ui/icon": "^3.2.0",
"@chakra-ui/popper": "^3.1.0",
"@chakra-ui/react-context": "^2.1.0",
"@chakra-ui/system": "^2.6.2",

@recs182
Copy link

recs182 commented Mar 6, 2025

The problem is at https://github.com/jeanverster/chakra-ui-steps library, I made a PR hoping they can get it fixed.
jeanverster/chakra-ui-steps#144

It would also required this library to be updated to use latest version...

The workaround mention above solves it but is not ideal.

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

No branches or pull requests

3 participants