TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

bug: TypeScript is not an ECMAScript superset post-ES2015

5 pointsby merrywhetherover 2 years ago

1 comment

karmakazeover 2 years ago
Can someone tell if this has much&#x2F;any practical significance? To me it seems to be a long pedantic discussion with little practical impact.<p>&gt; import { a } from &quot;.&#x2F;a&quot;<p>Seems to be the issue, maybe something about missing an extension.<p>&gt; Bearing this in mind, the last version of ES for which TypeScript was a superset would be ES5 (2009), before the introduction of ES modules.<p>This certainly matters to those writing ts -&gt; js transpilers. As far as I care, it doesn&#x27;t matter if the split happens at ES5 or ES2015 as long as the transpiled output works.<p>The fact that this detail is being raised seems like an indication of how well it conforms to being a superset, unlike CoffeeScript&#x27;s &quot;It&#x27;s just JavaScript.&quot; assertion.
评论 #32687887 未加载