Skip to content
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

fix!: import issue with ESM #125

Merged
merged 1 commit into from
Jul 3, 2023
Merged

Conversation

stainless-bot
Copy link
Collaborator

This change involves removing runtime exports for nested page class exports, which were only recently added
so we don't expect this breakage to affect anyone.

Migration

You can directly import the class instead of referencing it, e.g. import { FooPage } from 'pkg/resources/foo'

This change involves removing runtime exports for nested page class exports, which were only recently added
so we don't expect this breakage to affect anyone.

# Migration

You can directly import the class instead of referencing it, e.g. `import { FooPage } from 'pkg/resources/foo'`
@stainless-bot stainless-bot merged commit d8e6f99 into next Jul 3, 2023
@stainless-bot stainless-bot deleted the fix-import-issue-with-esm branch July 3, 2023 21:17
cleb11 pushed a commit that referenced this pull request Jul 7, 2023
This change involves removing runtime exports for nested page class exports, which were only recently added
so we don't expect this breakage to affect anyone.
# Migration
You can directly import the class instead of referencing it, e.g. `import { FooPage } from 'pkg/resources/foo'`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant