You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm the leader of a team that has been using TypeScript and Webpack together for a long time. I recently evaluated Parcel v2 as a replacement for Webpack in our projects, with hopes of simplifying our bundler configuration and speeding up compile times with swc.
For now, I've decided to stick with Webpack because it does not suffer from two key limitations in Parcel's support for TypeScript:
No support for baseUrl. See, for example, Usecase: Support for TypeScript TSConfig 'extends', 'baseUrl' and 'paths' #6073. I understand that ~ imports can be used instead, but this would change how we write our imports. Migrating an existing project to Parcel would require changing thousands of imports. Ideally, Parcel would support all tsconfig options.
Only experimental support for typechecking. I see there is an experimental plugin called @parcel/validator-typescript that does typechecking as part of the Parcel build. I just wanted to highlight this as an important feature that improves the developer experience. The alternative is to have two terminals, one running Parcel and one running tsc --watch. Which is fine, but I want to make the development workflow as simple as possible for my team.
Anyway, Parcel v2 looks very promising and keep up the great work!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I'm the leader of a team that has been using TypeScript and Webpack together for a long time. I recently evaluated Parcel v2 as a replacement for Webpack in our projects, with hopes of simplifying our bundler configuration and speeding up compile times with swc.
For now, I've decided to stick with Webpack because it does not suffer from two key limitations in Parcel's support for TypeScript:
No support for
baseUrl
. See, for example, Usecase: Support for TypeScript TSConfig 'extends', 'baseUrl' and 'paths' #6073. I understand that~
imports can be used instead, but this would change how we write our imports. Migrating an existing project to Parcel would require changing thousands of imports. Ideally, Parcel would support alltsconfig
options.Only experimental support for typechecking. I see there is an experimental plugin called
@parcel/validator-typescript
that does typechecking as part of the Parcel build. I just wanted to highlight this as an important feature that improves the developer experience. The alternative is to have two terminals, one running Parcel and one runningtsc --watch
. Which is fine, but I want to make the development workflow as simple as possible for my team.Anyway, Parcel v2 looks very promising and keep up the great work!
Beta Was this translation helpful? Give feedback.
All reactions