feat(ts): export types from entry point #4834
Merged
+2
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was changed in #4829, as i thought it was a mistake (like most of the other entries in that fake file), but /types is required
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit b77a1b0:
|
Haroenv
added a commit
that referenced
this pull request
Aug 17, 2021
This was changed in #4829, as i thought it was a mistake (like most of the other entries in that fake file), but /types is required
Haroenv
added a commit
that referenced
this pull request
Aug 17, 2021
This issue is caused by `export * from './types'` added in #4834, which causes everything in /types to be exposed, but unfortunately because `export from` in the InstantSearch file mixed a type and a value, and thus exported it. This is done by enabling [consistent-type-imports](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/consistent-type-imports.md) in eslint to make sure it's correct in all cases references: - code that throws: https://unpkg.com/browse/instantsearch.js@4.27.1/es/types/instantsearch.js - vite reproduction: https://github.com/eunjae-lee/vue-instantsearch-with-vue3-and-vite
Haroenv
added a commit
that referenced
this pull request
Aug 17, 2021
This issue is caused by `export * from './types'` added in #4834, which causes everything in /types to be exposed, but unfortunately because `export from` in the InstantSearch file mixed a type and a value, and thus exported it. This is done by enabling [consistent-type-imports](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/consistent-type-imports.md) in eslint to make sure it's correct in all cases references: - code that throws: https://unpkg.com/browse/instantsearch.js@4.27.1/es/types/instantsearch.js - vite reproduction: https://github.com/eunjae-lee/vue-instantsearch-with-vue3-and-vite
Haroenv
added a commit
that referenced
this pull request
Aug 17, 2021
This issue is caused by `export * from './types'` added in #4834, which causes everything in /types to be exposed, but unfortunately because `export from` in the InstantSearch file mixed a type and a value, and thus exported it. This is done by enabling [consistent-type-imports](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/consistent-type-imports.md) in eslint to make sure it's correct in all cases references: - code that throws: https://unpkg.com/browse/instantsearch.js@4.27.1/es/types/instantsearch.js - vite reproduction: https://github.com/eunjae-lee/vue-instantsearch-with-vue3-and-vite
Haroenv
added a commit
that referenced
this pull request
Aug 18, 2021
This issue is caused by `export * from './types'` added in #4834, which causes everything in /types to be exposed, but unfortunately because `export from` in the InstantSearch file mixed a type and a value, and thus exported it. This is done by enabling [consistent-type-imports](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/consistent-type-imports.md) in eslint to make sure it's correct in all cases references: - code that throws: https://unpkg.com/browse/instantsearch.js@4.27.1/es/types/instantsearch.js - vite reproduction: https://github.com/eunjae-lee/vue-instantsearch-with-vue3-and-vite
Haroenv
added a commit
that referenced
this pull request
Aug 18, 2021
This issue is caused by `export * from './types'` added in #4834, which causes everything in /types to be exposed, but unfortunately because `export from` in the InstantSearch file mixed a type and a value, and thus exported it. This is done by enabling [consistent-type-imports](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/consistent-type-imports.md) in eslint to make sure it's correct in all cases references: - code that throws: https://unpkg.com/browse/instantsearch.js@4.27.1/es/types/instantsearch.js - vite reproduction: https://github.com/eunjae-lee/vue-instantsearch-with-vue3-and-vite
Haroenv
added a commit
that referenced
this pull request
Aug 18, 2021
This issue is caused by `export * from './types'` added in #4834, which causes everything in /types to be exposed, but unfortunately because `export from` in the InstantSearch file mixed a type and a value, and thus exported it. This is done by enabling [consistent-type-imports](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/consistent-type-imports.md) in eslint to make sure it's correct in all cases references: - code that throws: https://unpkg.com/browse/instantsearch.js@4.27.1/es/types/instantsearch.js - vite reproduction: https://github.com/eunjae-lee/vue-instantsearch-with-vue3-and-vite
Haroenv
added a commit
that referenced
this pull request
Aug 18, 2021
This issue is caused by `export * from './types'` added in #4834, which causes everything in /types to be exposed, but unfortunately because `export from` in the InstantSearch file mixed a type and a value, and thus exported it. This is done by enabling [consistent-type-imports](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/consistent-type-imports.md) in eslint to make sure it's correct in all cases references: - code that throws: https://unpkg.com/browse/instantsearch.js@4.27.1/es/types/instantsearch.js - vite reproduction: https://github.com/eunjae-lee/vue-instantsearch-with-vue3-and-vite
Haroenv
added a commit
that referenced
this pull request
Aug 18, 2021
* fix(types): export all types as "type" to avoid exporting in .js This issue is caused by `export * from './types'` added in #4834, which causes everything in /types to be exposed, but unfortunately because `export from` in the InstantSearch file mixed a type and a value, and thus exported it. This is done by enabling [consistent-type-imports](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/consistent-type-imports.md) in eslint to make sure it's correct in all cases references: - code that throws: https://unpkg.com/browse/instantsearch.js@4.27.1/es/types/instantsearch.js - vite reproduction: https://github.com/eunjae-lee/vue-instantsearch-with-vue3-and-vite * fix ts * chore(ts): also enable `isolatedModules` this catches when you export something that's a type as a regular export, further avoiding the issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Types are useful outside of InstantSearch for for example Vue InstantSearch, React InstantSearch, so we want to expose this from the root
Result
This was changed in #4829, as i thought it was a mistake (like most of the other entries in that fake file), but /types is still useful