How to create a package with the isolatedModules=true option enabled?
In a file where I export all the classes of my package on lines like the following:
export {default as BoundList, IBoundListOption, TBoundListFilterFn} from './list/BoundList';
errors of the form are generated:
TS1205: Cannot re-export a type when the '--isolatedModules' flag is provided.
How do I export classes now?
This problem occurred in CRA2.1. There was forced to isolatedModules=true.
I'm making a component library on CRA2.1
reactjs typescript babeljs create-react-app
edited Dec 4 '18 at 18:55
Justin Grant
34.3k899155
asked Nov 23 '18 at 9:58
Khusamov SukhrobKhusamov Sukhrob
107111
add a comment |
In a file where I export all the classes of my package on lines like the following:
export {default as BoundList, IBoundListOption, TBoundListFilterFn} from './list/BoundList';
errors of the form are generated:
TS1205: Cannot re-export a type when the '--isolatedModules' flag is provided.
How do I export classes now?
This problem occurred in CRA2.1. There was forced to isolatedModules=true.
I'm making a component library on CRA2.1
reactjs typescript babeljs create-react-app
edited Dec 4 '18 at 18:55
Justin Grant
34.3k899155
asked Nov 23 '18 at 9:58
Khusamov SukhrobKhusamov Sukhrob
107111
github.com/babel/babel-loader/issues/603 Looks like there's some discussion here that includes workarounds.
– CollinD
Dec 4 '18 at 19:06
add a comment |
In a file where I export all the classes of my package on lines like the following:
export {default as BoundList, IBoundListOption, TBoundListFilterFn} from './list/BoundList';
errors of the form are generated:
TS1205: Cannot re-export a type when the '--isolatedModules' flag is provided.
How do I export classes now?
This problem occurred in CRA2.1. There was forced to isolatedModules=true.
I'm making a component library on CRA2.1
reactjs typescript babeljs create-react-app
edited Dec 4 '18 at 18:55
Justin Grant
34.3k899155
asked Nov 23 '18 at 9:58
Khusamov SukhrobKhusamov Sukhrob
107111
In a file where I export all the classes of my package on lines like the following:
export {default as BoundList, IBoundListOption, TBoundListFilterFn} from './list/BoundList';
errors of the form are generated:
TS1205: Cannot re-export a type when the '--isolatedModules' flag is provided.
How do I export classes now?
This problem occurred in CRA2.1. There was forced to isolatedModules=true.
I'm making a component library on CRA2.1
reactjs typescript babeljs create-react-app
reactjs typescript babeljs create-react-app
edited Dec 4 '18 at 18:55
Justin Grant
34.3k899155
asked Nov 23 '18 at 9:58
Khusamov SukhrobKhusamov Sukhrob
107111
edited Dec 4 '18 at 18:55
Justin Grant
34.3k899155
asked Nov 23 '18 at 9:58
Khusamov SukhrobKhusamov Sukhrob
107111
edited Dec 4 '18 at 18:55
Justin Grant
34.3k899155
edited Dec 4 '18 at 18:55
Justin Grant
34.3k899155
edited Dec 4 '18 at 18:55
Justin Grant
34.3k899155
34.3k899155
asked Nov 23 '18 at 9:58
Khusamov SukhrobKhusamov Sukhrob
107111
asked Nov 23 '18 at 9:58
Khusamov SukhrobKhusamov Sukhrob
107111
asked Nov 23 '18 at 9:58
Khusamov SukhrobKhusamov Sukhrob
107111
107111
github.com/babel/babel-loader/issues/603 Looks like there's some discussion here that includes workarounds.
– CollinD
Dec 4 '18 at 19:06
add a comment |
github.com/babel/babel-loader/issues/603 Looks like there's some discussion here that includes workarounds.
– CollinD
Dec 4 '18 at 19:06
github.com/babel/babel-loader/issues/603 Looks like there's some discussion here that includes workarounds.
– CollinD
Dec 4 '18 at 19:06
github.com/babel/babel-loader/issues/603 Looks like there's some discussion here that includes workarounds.
– CollinD
Dec 4 '18 at 19:06
add a comment |
2 Answers
2
active
oldest
votes
github.com/babel/babel-loader/issues/603 (thanks to @CollinD for the link) includes a workaround for how to re-export imported types. This comment on that issue has the best explanation of a workaround:
You can still do are-export if it's clear that you're exporting a type:
import { T as a_T } from "./a";
export type T = a_T;
You can also do
export * from "./a";.
If I'm reading that GitHub issue correctly, only TS types can be re-exported, but values (e.g. classes) can't be re-exported. So if TS knows that you're importing a type (not a class) then you can re-export it.
Here's another example that's simpler:
import { T } from "./a";
export type T = T;
answered Dec 13 '18 at 6:24
Justin GrantJustin Grant
34.3k899155
add a comment |
Yes - node_modules/fork-ts-checker-webpack-plugin/package.json is "version": "0.2.2".
It seems the change was made in Microsoft/TypeScript#15538 , so if you test with 2.3 you wouldn't see the error. But it will start breaking when 2.4 is released.
Still, none of this should be an issue if isolatedModules is overriden to true.
answered Dec 10 '18 at 12:14
SinghamSingham
575
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53444390%2fhow-to-create-a-package-with-the-isolatedmodules-true-option-enabled%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
github.com/babel/babel-loader/issues/603 (thanks to @CollinD for the link) includes a workaround for how to re-export imported types. This comment on that issue has the best explanation of a workaround:
You can still do are-export if it's clear that you're exporting a type:
import { T as a_T } from "./a";
export type T = a_T;
You can also do
export * from "./a";.
If I'm reading that GitHub issue correctly, only TS types can be re-exported, but values (e.g. classes) can't be re-exported. So if TS knows that you're importing a type (not a class) then you can re-export it.
Here's another example that's simpler:
import { T } from "./a";
export type T = T;
answered Dec 13 '18 at 6:24
Justin GrantJustin Grant
34.3k899155
add a comment |
github.com/babel/babel-loader/issues/603 (thanks to @CollinD for the link) includes a workaround for how to re-export imported types. This comment on that issue has the best explanation of a workaround:
You can still do are-export if it's clear that you're exporting a type:
import { T as a_T } from "./a";
export type T = a_T;
You can also do
export * from "./a";.
If I'm reading that GitHub issue correctly, only TS types can be re-exported, but values (e.g. classes) can't be re-exported. So if TS knows that you're importing a type (not a class) then you can re-export it.
Here's another example that's simpler:
import { T } from "./a";
export type T = T;
answered Dec 13 '18 at 6:24
Justin GrantJustin Grant
34.3k899155
add a comment |
github.com/babel/babel-loader/issues/603 (thanks to @CollinD for the link) includes a workaround for how to re-export imported types. This comment on that issue has the best explanation of a workaround:
You can still do are-export if it's clear that you're exporting a type:
import { T as a_T } from "./a";
export type T = a_T;
You can also do
export * from "./a";.
If I'm reading that GitHub issue correctly, only TS types can be re-exported, but values (e.g. classes) can't be re-exported. So if TS knows that you're importing a type (not a class) then you can re-export it.
Here's another example that's simpler:
import { T } from "./a";
export type T = T;
answered Dec 13 '18 at 6:24
Justin GrantJustin Grant
34.3k899155
github.com/babel/babel-loader/issues/603 (thanks to @CollinD for the link) includes a workaround for how to re-export imported types. This comment on that issue has the best explanation of a workaround:
You can still do are-export if it's clear that you're exporting a type:
import { T as a_T } from "./a";
export type T = a_T;
You can also do
export * from "./a";.
If I'm reading that GitHub issue correctly, only TS types can be re-exported, but values (e.g. classes) can't be re-exported. So if TS knows that you're importing a type (not a class) then you can re-export it.
Here's another example that's simpler:
import { T } from "./a";
export type T = T;
answered Dec 13 '18 at 6:24
Justin GrantJustin Grant
34.3k899155
edited Mar 18 at 23:44
answered Dec 13 '18 at 6:24
Justin GrantJustin Grant
34.3k899155
answered Dec 13 '18 at 6:24
Justin GrantJustin Grant
34.3k899155
answered Dec 13 '18 at 6:24
Justin GrantJustin Grant
34.3k899155
34.3k899155
add a comment |
add a comment |
Yes - node_modules/fork-ts-checker-webpack-plugin/package.json is "version": "0.2.2".
It seems the change was made in Microsoft/TypeScript#15538 , so if you test with 2.3 you wouldn't see the error. But it will start breaking when 2.4 is released.
Still, none of this should be an issue if isolatedModules is overriden to true.
answered Dec 10 '18 at 12:14
SinghamSingham
575
add a comment |
Yes - node_modules/fork-ts-checker-webpack-plugin/package.json is "version": "0.2.2".
It seems the change was made in Microsoft/TypeScript#15538 , so if you test with 2.3 you wouldn't see the error. But it will start breaking when 2.4 is released.
Still, none of this should be an issue if isolatedModules is overriden to true.
answered Dec 10 '18 at 12:14
SinghamSingham
575
add a comment |
Yes - node_modules/fork-ts-checker-webpack-plugin/package.json is "version": "0.2.2".
It seems the change was made in Microsoft/TypeScript#15538 , so if you test with 2.3 you wouldn't see the error. But it will start breaking when 2.4 is released.
Still, none of this should be an issue if isolatedModules is overriden to true.
answered Dec 10 '18 at 12:14
SinghamSingham
575
Yes - node_modules/fork-ts-checker-webpack-plugin/package.json is "version": "0.2.2".
It seems the change was made in Microsoft/TypeScript#15538 , so if you test with 2.3 you wouldn't see the error. But it will start breaking when 2.4 is released.
Still, none of this should be an issue if isolatedModules is overriden to true.
answered Dec 10 '18 at 12:14
SinghamSingham
575
answered Dec 10 '18 at 12:14
SinghamSingham
575
answered Dec 10 '18 at 12:14
SinghamSingham
575
answered Dec 10 '18 at 12:14
SinghamSingham
575
575
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53444390%2fhow-to-create-a-package-with-the-isolatedmodules-true-option-enabled%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
github.com/babel/babel-loader/issues/603 Looks like there's some discussion here that includes workarounds.
– CollinD
Dec 4 '18 at 19:06