not support parcel@1.10

[nnecec]

Throw error when update parcel to 1.10.
Look like typescript compile failure.
Maybe because parcel@1.10 support babel@7, I don't know ..

[cyntler]

Exactly. This is happening. When I made the parcel-bundler downgrade to 1.9.4 everything works fine.

[mironal]

You can use tsc -noEmit instead of parcel-plugin-typescript.

Because parcel-plugin-typescript is mainly used only for type check.

ex.

{
    "scripts": {
        "build": "parcel build src/index.ts --target node"
    }
}

to

{
    "scripts": {
        "build": "tsc - no Emit && parcel build src/index.ts --target node"
    }
}

[mnn]

Yeah, it seems TypeScript files aren't being processed by tsc.

$ npx parcel build src/index.ts
🚨  SyntaxError: /xxx/src/index.ts: Unexpected token, expected ";" (7:5)

   5 | import * as fp from 'fp-ts';
   6 | 
>  7 | var a: string = '';
     |      ^

Versions:
parcel-bundler@1.10.3
parcel-plugin-typescript@1.0.0

[cruhl]

I'm having the same issue

[TkDodo]

You can use tsc -noEmit instead of parcel-plugin-typescript.

As far as I know, absolute imports are not working with parcel if you are not using parcel-plugin-typescript, so I need that plugin to work. Unfortunately, I am having the same issue when upgrading to 1.10.3

[mmmeff]

This is a really bad bug. First noticed it while learning Parcel on codesandbox, attributed it to the platform, started a new project locally and I'm still having issues compiling typescript files. Any typescript-specific syntax breaks the compiler. Both .ts and .tsx file extensions break parcel.

[joseluisq]

Any updates? I have the same issue:

  "parcel-bundler": "^1.10.3",
  "parcel-plugin-typescript": "^1.0.0"

[mitchellnemitz]

I solved this issue by abandoning this plugin and instead installing @babel/preset-typescript and babel-plugin-module-resolver with this bit of config in my .babelrc:

{
    "presets": [
        ...
        "@babel/preset-typescript"
    ],
    "plugins": [
        [
            "module-resolver", {
                "alias": { ... },
                "root": ["./same/as/tsconfig.json/baseUrl"],
                "extensions": [".js", ".jsx", ".ts", ".tsx"]
            }
        ]
    ]
}

[benpolinsky]

@mitchellnemitz this "works" but still doesn't report errors on build.

Edit: unless I am missing something, which could very well be the case :)

[quantuminformation]

same issue?

#13 (comment)

[mitchellnemitz]

@benpolinsky if you add "noEmit": true to your tsconfig.json you can just run tsc in parallel with your build to find any type errors. The point of using babel instead of typescript directly is just to speed up build and move type checking to more of a lint-type situation that can be run in parallel, which can be a good or bad thing depending on your goals and mentality.