Repository navigation
Entry points fail without import/export statements #357
Description
For files that don't have import or export statements ts-node test.ts fails when there is await function:
ReferenceError: __awaiter is not defined
test.ts
(async () => {})().catch(console.error);
tsconfig.json
{
"compilerOptions": {
"target": "es6",
"module": "commonjs",
"moduleResolution": "node",
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"allowSyntheticDefaultImports": true,
"alwaysStrict": true,
"sourceMap": true,
"noEmitHelpers": true,
"importHelpers": true,
"strictNullChecks": false,
"baseUrl": ".",
"paths": [],
"lib": [ "es2017"]
},
"exclude": [
"node_modules",
"dist"
]
}
Of course, tslib is installed. And it starts working normally when export default {} is added.
It was different in older ts-node before it was updated (likely 2.x), an error appeared for all module-scoped const:
Cannot redeclare block-scoped variable ...
And it disappeared when import or export statements were added, so it looks like a file wasn't compiled as ES6 module.
ts-node 3.0.4,
typescript 2.3.4
tslib 1.7.1
node 6.10.3
Activity
blakeembrey commentedon Jun 15, 2017
This isn't an issue with
ts-node. Most likely the different issues have appeared or disappeared based on you updating external factors such as TypeScript or node.js. If I compile usingtsc, there's no error from TypeScript and I can easily see why this is an error:bisubus commentedon Jun 15, 2017
@blakeembrey Thanks for the clarification, it makes sense. I've encountered some mentions of this TS trait like microsoft/TypeScript#12167 , still looks obscure and bug-like.
blakeembrey commentedon Jun 15, 2017
It's unfortunate though. You'd think TypeScript would flag this as an error, but I suppose "technically" you did ask for
noEmitHelpersandimportHelpersdoesn't make sense for a global script.