Skip to content

update import aliases to new format#18

Merged
james-elicx merged 1 commit intomainfrom
j-branch-6
Feb 2, 2026
Merged

update import aliases to new format#18
james-elicx merged 1 commit intomainfrom
j-branch-6

Conversation

@james-elicx
Copy link
Collaborator

  • Updates all import aliases to use the same format (prefixed with @/)

@pkg-pr-new
Copy link

pkg-pr-new bot commented Feb 2, 2026

Open in StackBlitz

npm i https://pkg.pr.new/@opennextjs/cloudflare@18
npm i https://pkg.pr.new/@opennextjs/aws@18

commit: 7ab3788

@james-elicx james-elicx linked an issue Feb 2, 2026 that may be closed by this pull request
@james-elicx james-elicx marked this pull request as ready for review February 2, 2026 18:29
@james-elicx james-elicx requested review from sommeeeer and vicb February 2, 2026 18:29
Copy link
Contributor

@vicb vicb left a comment

Choose a reason for hiding this comment

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

LGTM if it builds and passes the tests.

Do we actually need aliases ?
My (maybe outdated) feeling is that they only bring issues.
But ok to merge this for now for consistency and discuss later if needed

@james-elicx
Copy link
Collaborator Author

Do we actually need aliases ?
My (maybe outdated) feeling is that they only bring issues.
But ok to merge this for now for consistency and discuss later if needed

Nah we don't need them, but there seems to be a lot of usage in aws. I imagine that a lot of imports might change as separate aws and core, so that might be a pathway to phasing out potentially

@james-elicx james-elicx merged commit 9cbe4cf into main Feb 2, 2026
6 checks passed
@james-elicx james-elicx deleted the j-branch-6 branch February 2, 2026 18:38
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.

align import alias usage

2 participants