Skip to content

Use "import * as ___" with a separate "export { ___ }" declaration - #743

Closed
aalmada wants to merge 1 commit into
dethcrypto:masterfrom
aalmada:ImportExport
Closed

Use "import * as ___" with a separate "export { ___ }" declaration#743
aalmada wants to merge 1 commit into
dethcrypto:masterfrom
aalmada:ImportExport

Conversation

@aalmada

@aalmada aalmada commented Jul 22, 2022

Copy link
Copy Markdown

Use

import type * as factories from "./factories";
export type { factories };

instead of

export * as factories from "./factories";

A workaround because api-exporter does not support the one-liner export.

Fixes #742

Passed all the unit tests.

@changeset-bot

changeset-bot Bot commented Jul 22, 2022

Copy link
Copy Markdown

鈿狅笍 No Changeset found

Latest commit: 7c9d643

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@aalmada

aalmada commented Aug 1, 2022

Copy link
Copy Markdown
Author

@krzkaczor Hi! Any chance there will be a new release soon containing this PR?

@aalmada aalmada closed this by deleting the head repository Dec 27, 2023
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.

Use "import * as ___" with a separate "export { ___ }" declaration

1 participant