feat: change yarn dev to use gulp

[noname0310]

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• It's submitted to the dev branch, not the main branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• All tests are passing
• New/updated tests are included

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

• Since the bug in ts-macros has been fixed, it is now possible to hot reload with gulp So I changed the yarn dev.
  [BUG] error when build twice GoogleFeud/ts-macros#15

• Results built through yarn dev are now identical to cjs builds, excluding source maps.

• The hot reload is a little slow because we are currently using the babel and terser.
  If you want a faster hot reload, you can also exclude it from dev mode.
  However, there will be a slight difference between the results from dev mode and the build results.

• Builds in dev mode are now created in dist/dev.

[coveralls]

Coverage remained the same at 100.0% when pulling 62b6815 on noname0310:fix/update-ts-macro into 7a28c07 on js-sdsl:dev.

[ZLY201]

Does yarn dev run quickly?

[noname0310]

Does yarn dev run quickly?

It takes longer than before, but now the dev build is the same as the production build result.

And you wanted to get rid of tsconfig.dev.json and build it the same way

[ZLY201]

'dist/cjs'

[noname0310]

okay

[noname0310]

I just tried building with minimal code except for babel and terser, and it came out in 13 seconds.
I think it must take more than 12 seconds to hot load with gulp typescript.

it takes 12~13 seconds on hot reload:

const project = gulpTs.createProject('tsconfig.json');

gulp.task('build', () => {
  return gulp.src('src/**/*.ts', { base: 'src' })
    .pipe(project())
    .pipe(gulp.dest('dist'));
});

gulp.task('watch',
  gulp.series(
    'ts',
    function watch() {
      return gulp.watch('src/**/*.ts', gulp.series('build'));
    }
  )
);

https://github.com/ivogabe/gulp-typescript#incremental-compilation

[noname0310]

It seems better to update ts-macro. By the way, if you don't like slow gulp hot reload, I'll rollback gulp dev build

[ZLY201]

It seems better to update ts-macro. By the way, if you don't like slow gulp hot reload, I'll rollback gulp dev build

It's ok, the dev mode should be as consistent as possible with thebuildmode.

But we also should try to reduce the complie time.

[noname0310]

It seems better to update ts-macro. By the way, if you don't like slow gulp hot reload, I'll rollback gulp dev build

It's ok, the dev mode should be as consistent as possible with thebuildmode.

But we also should try to reduce the complie time.

okay, I'll find a way to speed up the typescript hot reload

Then, I will prioritize umd build support I think it will take more time to improve the hot reload time

[ZLY201]

It seems better to update ts-macro. By the way, if you don't like slow gulp hot reload, I'll rollback gulp dev build

It's ok, the dev mode should be as consistent as possible with thebuildmode.
But we also should try to reduce the complie time.

okay, I'll find a way to speed up the typescript hot reload

Then, I will prioritize umd build support I think it will take more time to improve the hot reload time

That's ok.