-
Notifications
You must be signed in to change notification settings - Fork 190
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
[Bug]: Major breaking change in some recent release #1954
Comments
Same here:
"@carbon/charts-react": "1.22.11" works for us, but, after that fails. The basic issue is jsx-runtime is a file, not a folder. See https://cdn.jsdelivr.net/npm/[email protected]/jsx-runtime.js. ESM modules require files to include extensions now, whereas CJS imports would automatically check for .json, .js, etc if the extension was not specified. |
As created and tested the issue using a StackBlitz setup that closely mirrors our codebase configuration. The problem started when I attempted to use the latest After reviewing the release notes of charts-react, I noticed that starting from Environment: |
Hi @TannerS - I was looking at the StackBlitz repro you provided above and something that caught my eye... "@carbon/charts": "^0.54.12",
"@carbon/charts-react": "^1.22.0" Looks like you are just using the CSS from @carbon/charts. These can be imported directly from @carbon/charts-react so you don't need @carbon/charts and even if you do want to do a direct import from it, you will want to use the same version. The latest is Also, you mentioned you are having to upgrade dependencies in the project right now. Would it be possible to at least upgrade to React 17 (if not 19)? |
nstuyvesant That StackBlitz was created purely for experimental purposes to reproduce the issue and doesn’t reflect any specific standards for library usage. I do understand that @carbon/charts-react alone is sufficient for styling, but since my focus was on reproducing the issue, I didn’t pay much attention to version alignment or optimization. The setup was left as is while making changes in the codebase. |
@arjunkgit - Do you still have issues with 1.22.16? |
No issues, 1.22.16 is working fine for us. |
@TannerS - did 1.22.16 resolve your issue? |
Sorry give me time I been out side and have some project deadlines to meet
Sent from my T-Mobile 5G Device
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Nate Stuyvesant ***@***.***>
Sent: Wednesday, February 12, 2025 12:25:17 PM
To: carbon-design-system/carbon-charts ***@***.***>
Cc: Tanner Summers ***@***.***>; Mention ***@***.***>
Subject: Re: [carbon-design-system/carbon-charts] [Bug]: Major breaking change in some recent release (Issue #1954)
@TannerS<https://github.com/TannerS> - did 1.22.16 resolve your issue?
—
Reply to this email directly, view it on GitHub<#1954 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACDUUD47BAZWZFT2VRUAZZL2POGY3AVCNFSM6AAAAABWWMNK4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJUGUZDGMBSHA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Relevant package(s)
Carbon Charts Version
^1.22.7
Which bundler are you using?
Webpack
What happened and what did you expect to happen?
We havev't touched our code in a long time, but we have to update the dependencies to fix vuln. In our service, we ran npm install and it updated
"@carbon/charts-react": "^1.22.7"
to some new version. When it did, we pushed our code to the console (ibm cloud) pipeline and during the stage to build webpack, we got thisThere is a slack convo going on with this with others having same issue
https://ibm-cloudplatform.slack.com/archives/CCA7L4MS9/p1738862305761429
Chart data and options (automatically formatted so no need for backticks)
JavaScript console or build output (if relevant)
StackBlitz repro
https://stackblitz.com/edit/github-1qm8hle9?file=package.json,webpack.config.js,.babelrc,src%2Findex.js,dist%2Findex.html,package-lock.json&file=package.json&terminal=
IBM Application/Team (if relevant)
Multiple teams
What priority level would this be in your opinion?
P0 (Critical)
The text was updated successfully, but these errors were encountered: