Babel overwrites target ecmaVersion of tsconfig

[DeMoorJasper]

🐛 bug report

🎛 Configuration (.babelrc, package.json, cli command)

tsconfig => es2018
babel => no config

🤔 Expected Behavior

Babel shouldn't transpile down

😯 Current Behavior

Babel does transpile down

💁 Possible Solution

Check if it's already transpiled in JSAsset.parse and just convert to a babel ast if it has been

🔦 Context

See twitter conversation: https://twitter.com/martin_hotell/status/965862279022632961

💻 Code Sample

🌍 Your Environment

Accurs in all parcel versions

[Hotell]

Just adding more info:

TS version: 2.7.2

tsconfig.json

{
  "compilerOptions": {
    "target": "esnext",
    "sourceMap": true, 
    "importHelpers": true,
    "pretty": true,
    "skipLibCheck": true,
    "strict": true, 
    "moduleResolution": "node",
    "esModuleInterop": true                     
  }
}

[devongovett]

In the latest Parcel version, we apply babel-preset-env by default. If you don't specify browser targets, we'll choose a set of default browser targets (> 1% marketshare). This means your code will be transpiled by babel after typescript runs. You can stop this from happening by setting some browser targets for your app in package.json:

{
  "browserslist": ["last 2 Chrome versions"]
}

[dkundel]

Is there no way to take a hint from the tsconfig.json if we are bundling TypeScript and configuring babel-present-env according to that information.

Like if there is no .babelrc and no browserslist entry but we are bundling TypeScript check which value is used in target in the config to determine the output.

This seems to be the same issue raised in #954

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.