-
Notifications
You must be signed in to change notification settings - Fork 9
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
Icons: fix having to import from /dist #417
Icons: fix having to import from /dist #417
Conversation
🦋 Changeset detectedLatest commit: 39ec05b The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -1,7 +1,7 @@ | |||
import { type StoryObj, type Meta } from "@storybook/react"; | |||
import Badge from "./Badge"; | |||
import RepeatIcon from "@mui/icons-material/Repeat"; | |||
import Refresh from "../../../syntax-icons/src/Refresh"; | |||
import Refresh from "../../../syntax-icons/src/icons/Refresh"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@somethiiing moved these into icons
to be able to quickly get a list of all the different icons
(excluding tests / stories or other files)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh man, i wanted to do this before, but i remember you wanted to keep it flatter in core so i kept it this way
import path from "node:path"; | ||
|
||
describe("package.json: exports", () => { | ||
it("contains correct exports", async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@somethiiing added a test to ensure we use have the correct exports
field
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG thanks for following up on this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for doing this, i was going to do it yesterday, but got pulled into some meetings. great job though!
Why is this a breaking change?
Previous imports including
/dist
will no longer work, example change when this lands:Why is this no longer an issue in Cambly-Frontend
Since we now use a new module resolution: https://github.com/Cambly/Cambly-Frontend/pull/9878
Notes