Repository navigation
Re-exporting type declaration fails with "transpileOnly": true #1353
Description
Expected Behavior
I expect that running the code below will succeed:
lib.ts
export class PersonClass {
age: number;
}
export type PersonType = {
name: string;
}index.ts
export { PersonClass, PersonType } from './lib';Actual Behavior
Indeed it does, unless tsconfig.json also contains "ts-node": { "transpileOnly": true }, in which case it fails with:
export { PersonClass, PersonType } from './lib';
^^^^^^^^^^
SyntaxError: The requested module './lib' does not provide an export named 'PersonType'
Steps to reproduce the problem
node --loader=ts-node/esm --experimental-specifier-resolution=node index.ts
Minimal reproduction
https://github.com/dandv/ts-node-1353
Specifications
- ts-node version: 10.0.0
- node version: 16.2.0 or 15.14.0
- TypeScript version: 4.3.2
- tsconfig.json, if you're using one:
{
"ts-node": {
"transpileOnly": true
},
"compilerOptions": {
"target": "esnext",
"module": "esnext"
}
}
- Operating system and version: Ubuntu 20
Activity
cspotcode commentedon May 28, 2021
I'm not sure, but you may need to split your
export {} fromonto 2 lines, one beingexport {}and the other beingexport type{}I suggest turning on
isolatedModulesand then seeing iftsccomplains.isolatedModulescan be a bit confusing, but essentially it tells the typechecker to complain any time you're doing something that might break intranspileOnlymode.I expect that
isolatedModuleswill complain, but that you'll be able to fix the problem like this, or something very similar to this:cspotcode commentedon May 28, 2021
TypeScript's handbook explains the purpose of isolatedModules very well.
https://www.typescriptlang.org/tsconfig#isolatedModules
dandv commentedon May 28, 2021
Indeed,
isolatedModuleswarns,Explicitly adding the
export typesolved the issue. Thanks @cspotcode!