test: switch to experimental built-in type stripping

[AugustinMauroy]

• test suite time 29s => 25s

[AugustinMauroy]

test are failing for something look like not related to this pr

[aduh95]

test are failing for something look like not related to this pr

What makes you think that? AFAICT it's definitely related to this PR

[AugustinMauroy]

my bad

[aduh95]

I'm getting the following error when I try your branch:

$ yarn build --force  
packages/crypto/tsconfig.json:4:35 - error TS5096: Option 'allowImportingTsExtensions' can only be used when either 'noEmit' or 'emitDeclarationOnly' is set.

4     "allowImportingTsExtensions": true,
                                    ~~~~


Found 1 error.

[aduh95]

BTW I wonder if a better approach would be to split it into several PRs:

1. Switch the custom loader to use the built-in type stripping instead of sucrase.
2. Remove custom test file?
3. Update the specifiers in the source files.
4. Remove the loader eventually.

[AugustinMauroy]

BTW I wonder if a better approach would be to split it into several PRs:

1. Switch the custom loader to use the built-in type stripping instead of sucrase.
2. Update the specifiers in the source files.
3. Remove the loader eventually.

1. Maybe we should put the build in the CI.
2. I'm not in favor of multiple PRs because the work isn't huge and 80% is already done. All that's left is to fix the build.

[aduh95]

I'm not in favor of multiple PRs because the work isn't huge and 80% is already done. All that's left is to fix the build.

How much of the job is done is kinda irrelevant, it should be split nonetheless IMO

[aduh95]

I've opened #68 to cover the first step