-
Notifications
You must be signed in to change notification settings - Fork 325
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
chore: housekeeping 2 - emit ts-sourcemaps & monorepo config stuff #103
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
async onSuccess() { | ||
// emit sourcemap to enable jump to definition | ||
execSync("pnpm tsc --project tsconfig.sourcemap.json"); | ||
}, |
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 is the stuff that generates the sourcemaps that allows jump-to-definition
"@ianvs/prettier-plugin-sort-imports", | ||
"prettier-plugin-tailwindcss", | ||
], | ||
importOrder: [ |
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.
Can you add "<TYPES>"
to the end of the sort order? Mixing type imports with regular imports gets a bit confusing at times.
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.
you want separate type imports? so like
import { foo } from "foo";
import type { Bar } from "foo";
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.
Yes, exactly.
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.
Not excited for the merge conflict I'm about to eat on the v4 PR lol
DW I'll resolve it all 😇 |
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.
Just a few nits.
@@ -115,10 +117,13 @@ The `@uploadthing/solid` package includes an "Uploader" component that you can s | |||
```tsx copy | |||
// You need to import our styles for the button to look right. Best to import in the root /layout.tsx but this is fine | |||
import "@uploadthing/solid/styles.css"; | |||
|
|||
import { type VoidComponent } from "solid-js"; |
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.
Is there anything we can do to prefer
import type { ... } from "some-package"
over
import { type ... } from "some-package"
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.
I don't know if there is a way to force you to change inline-type to separate ones, but with the current setup the auto fix is set to use separate-types.
Maybe the eslint-plugin-import has an option for this
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.
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.
CleanShot.2023-05-28.at.10.00.03.mp4
now only top-level are allowed
CleanShot.2023-05-26.at.23.38.09.mp4