Skip to content

Switch to NodeNext module resolution #2478

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

Merged

Conversation

KevinGhadyani-Okta
Copy link
Contributor

OKTA-856735

Summary

Odyssey was using Bundler to build rather than NodeNext. This requires consumers to make changes to their TSConfig files. We don't want that.

After the recent changes to upgraded packages, we need to add .js to each local import with NodeNext module resolution.

Testing & Screenshots

  • I have confirmed this change with my designer and the Odyssey Design Team.

@KevinGhadyani-Okta KevinGhadyani-Okta requested a review from a team as a code owner January 23, 2025 19:59
import { type PaginationProps } from "../../Pagination";
import { RowActionsProps } from "./RowActions";
} from "./dataTypes.js";
import { MenuButtonProps } from "../../index.js";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it was "bad" before your change, but I'd recommend have this pull from Buttons/index.js (or wherever it is) rather than the top-level index.js

@oktapp-aperture-okta oktapp-aperture-okta bot merged commit 2510a72 into main Jan 23, 2025
1 check passed
@oktapp-aperture-okta oktapp-aperture-okta bot deleted the kg_use-nodenext-module-resolution-OKTA-856735 branch January 23, 2025 22:32
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

Successfully merging this pull request may close these issues.

2 participants