-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publishing fork under a new name #14
Comments
it will bring a bit migration cost, but I'm open to change it, do you have a better name? 😄 |
@aladdin-add Hello Man i loved your work, i have also been working on bringing this project back to live. Are you interested in a chat? I think @Fedeorlandau is right, it would be best to bring the changes and improvements under a new name as it will be simpler to distinguish. How about TS-build? actually I have been playing around esbuild trying to implement something like tsdx but when I saw your fork I thought it's better to learn and contribute here only. Btw I think it's best to ditch parcel for the example playground as it's bringing some issues and breaking HMR. |
Due to this issue, i decided to replace it with Vite, a build tool which uses esBuild and rollup both. and with a few changes, the dev server including HMR works like a charm Which left me thinking, we could use this https://github.com/egoist/rollup-plugin-esbuild to harness the power of esbuild ? |
:+1 SGTM! let's chat here: https://discord.gg/fMDeSvvm2p |
ts-publish (tsp) is my recommendation since this is for publishing ts packages lol ts-publish (tsp) |
@sidwebworks recommended
just let me know what you think. :) |
Sounds great! |
Alright guys, got the first PR going! let's see how it goes |
dts-cli v0.17.0 was released. :🎉 |
First let me thank you for your amazing work on this fork.
It would be nice that all of this effort gets more recognition. It's actually not that straightforward to land on this repository.
Have you considered publishing this package under a new name?
Regards,
The text was updated successfully, but these errors were encountered: