Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

[Bug] Back to tsc and ts-node #132

Closed
7 tasks done
barthofu opened this issue Dec 4, 2023 · 0 comments
Closed
7 tasks done

[Bug] Back to tsc and ts-node #132

barthofu opened this issue Dec 4, 2023 · 0 comments
Assignees
@barthofu
Labels
bug Something isn't working
Milestone
v2.3

Comments

@barthofu
Copy link
Owner

barthofu commented Dec 4, 2023 •
edited
Loading

What happened?

swc is way too unstable.

We should re-run comparative tests against tsc and ts-node and make a decision about going back to them or not.
This must also take in account the potentially new HMR solution.

In the end, we should have a balanced solution between DX and stability.

Tests

  • npm run dev
  • npm run build -> npm run start
  • docker
  • pm2
  • dev and build/start with plugins
  • windows
  • linux

Related
@barthofu barthofu added the bug Something isn't working label Dec 4, 2023
@barthofu barthofu added this to the v2.3 milestone Dec 4, 2023
@barthofu barthofu self-assigned this Dec 4, 2023
@barthofu barthofu changed the title [Bug] swc [Bug] Back to tsc and ts-node Dec 4, 2023
barthofu added a commit that referenced this issue Dec 4, 2023
@barthofu
feat(#132): switching from swc to tsc
8e673a9 
`swc`, despite being a little faster, was involving way too much random issues and wasn't stable at all.
barthofu added a commit that referenced this issue Dec 4, 2023
@barthofu
feat(#132): switching from swc to tsc
d0ac509 
`swc`, despite being a little faster, was involving way too much random issues and wasn't stable at all.
barthofu added a commit that referenced this issue Dec 4, 2023
@barthofu
feat(#132): switching from swc to tsc
a990bef 
`swc`, despite being a little faster, was involving way too much random issues and wasn't stable at all.
@barthofu barthofu closed this as completed Dec 4, 2023
barthofu added a commit that referenced this issue Dec 4, 2023
@barthofu
feat(#132): switching from swc to tsc
828866e 
`swc`, despite being a little faster, was involving way too much random issues and wasn't stable at all.
barthofu added a commit that referenced this issue Feb 21, 2024
@barthofu
feat(#132): switching from swc to tsc
a526e16 
`swc`, despite being a little faster, was involving way too much random issues and wasn't stable at all.
barthofu added a commit that referenced this issue Mar 4, 2024
@barthofu
feat(#132): switching from swc to tsc
a13b439 
`swc`, despite being a little faster, was involving way too much random issues and wasn't stable at all.
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@barthofu barthofu

Labels
bug Something isn't working
Projects
None yet
Milestone
v2.3
Development

When branches are created from issues, their pull requests are automatically linked.

132-bug-back-to-tsc-and-ts-node barthofu/tscord
1 participant
@barthofu