Skip to content

Unable to Complete v3 Upgrade with @siemens/ix-react #1859

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

Open
2 tasks done
mhSiemens opened this issue Apr 27, 2025 · 1 comment
Open
2 tasks done

Unable to Complete v3 Upgrade with @siemens/ix-react #1859

mhSiemens opened this issue Apr 27, 2025 · 1 comment
Labels
needs reproduction Bugs with the label will not be addressed until the steps to reproduce are available triage We discuss this topic in our internal weekly

Comments

@mhSiemens
Copy link

Prerequisites

  • I have read the Contributing Guidelines.
  • I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

What happened?

Description
I recently upgraded all IX libraries (@siemens/ix, @siemens/ix-icons, and @siemens/ix-react).
On first use of @siemens/ix-react, I encountered the following error:

Module not found: Error: Package path . is not exported from package C:\testrepo\node_modules\@siemens\ix-react (see exports field in C:\testrepo\node_modules\@siemens\ix-react\package.json)

Node Version: v22.14.0
React Version: 18.2.0
Webpack Version: 5.99.0

What type of frontend framework are you seeing the problem on?

React

Which version of iX do you use?

v3.0.0

Code to produce this issue.

import { IxDropdownButton, IxDropdownItem, IxLinkButton } from "@siemens/ix-react"
@mhSiemens mhSiemens added the triage We discuss this topic in our internal weekly label Apr 27, 2025
@danielleroux danielleroux added the needs reproduction Bugs with the label will not be addressed until the steps to reproduce are available label Apr 28, 2025
Copy link
Contributor

Thank you for creating this issue! It has been labeled as needs reproduction.

To help us assist you better, could you please provide a way for us to access the code (such as a GitHub repository or a StackBlitz link). Without a reliable code reproduction, it might be challenging for us to resolve the issue, and we may have to close it.
Thank you for your understanding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs reproduction Bugs with the label will not be addressed until the steps to reproduce are available triage We discuss this topic in our internal weekly
Projects
None yet
Development

No branches or pull requests

2 participants