-
-
Notifications
You must be signed in to change notification settings - Fork 755
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
convert to tsup #2652
convert to tsup #2652
Conversation
🦋 Changeset detectedLatest commit: a0d56f4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 56 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Thank you @shahriar-shojib for this first contribution! |
config/tsup.config.ts
Outdated
cjsInterop: true, | ||
dts: true, | ||
replaceNodeEnv: true, | ||
skipNodeModulesBundle: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this will skip bundling of anything imported that is not local to the package even if it is a dependency.
Ideally, for packages like these, I think it's best not to bundle node_module packages in the build files since it will be taken care of by the end user's bundler.
Since we're not shipping browser bundles this provides some safety in my opinion.
If you think this is unnecessary I can remove it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will test it on next release
I am not sure why the preview builds are failing, and I am unable to check the vercel logs. |
I am unsure if tailwind, babel, and JSON to esmodule support are necessary for the builds. |
Tailwind and json are not. If there is no regression without Babel, we could proceed without it. Note that The CI that is failing is |
I was able to run the test locally and it passed, CI logs are not showing why exactly the tests are failing, I will dig into it. Could I get some logs from Vercel, please? |
ok so, I was able to get it run completely after adjusting a few values on concurrency, it was timing out on my repo. Here's what I suspect is going on: I think turbo runs tasks with parallel task count equal to host logical cores, and jest runs tests in parallel which equals to host logical CPU count too. I have some further adjustments to make to make sure we're using the system to its fullest potential. Also, what are your thoughts on using @swc/jest ? my test run: https://github.com/shahriar-shojib/plate/actions/runs/6343411359 |
as for vercel deployment I am unable to figure out why it's failing, as you can see from the CI outputs it does not fail at the build step. |
Thanks for suggesting @swc/jest, tests were a bit slow so let's use it. As for Vercel, there is no error except |
switch to @swc/core nextjs conditional config revert ci edits
@shahriar-shojib Could we use https://github.com/gajus/turbowatch? Ref: vercel/turborepo#986 (comment) |
I have fixed the |
This looks nice, but I just added turbowatch and moved build:watch to use turbowatch |
please let me know if you need to build the dependents of a changed package |
Excellent job, thanks! Turbowatch is doing exactly what we needed so you can remove tsx package and As for building dependents, it's just about running |
convert AnyObject from interface to type convert TElement from interface to type convert TTest from interface to type remove tsx package & dev script
I fixed this by converting AnyObject, TElement, TTest from interface to type. Should not cause any breaking changees. |
Will check when I get back
On Sep 30, 2023, at 10:29 PM, Ziad Beyens ***@***.***> wrote:
@shahriar-shojib<https://github.com/shahriar-shojib> We have a single type error in the playground template:
[2023-09-30 at 18 27 31]<https://user-images.githubusercontent.com/19695832/271784254-f4173222-8722-4c8f-9365-c28201e06a34.png>
Could you take a look? Will tip $50 for that one 🙂
—
Reply to this email directly, view it on GitHub<#2652 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABRUFBTNJEAWTRIWL4JMXYDX5BCGBANCNFSM6AAAAAA5KZZBF4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Description
implements #2627
checklist:
@swc/core
regressions/claim #2627
keeping this as draft so that I can run some tests
See changesets.