fix: can't build package on windows #1894
Conversation
|
|
@AkaraChen is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
packages/nextra/tsup.config.ts
Outdated
| @@ -14,6 +14,8 @@ const CLIENT_ENTRY = [ | |||
| const entries = fg.sync(CLIENT_ENTRY, { absolute: true }) | |||
| const entriesSet = new Set(entries) | |||
|
|
|||
| const winPath = (p: string) => p.replace(/\\/g, '/') | |||
There was a problem hiding this comment.
Could you use slash package for this case (he is already installed in nextra)
There was a problem hiding this comment.
Could you use
slashpackage for this case (he is already installed in nextra)
Edited
* fix: can't build package on windows * chore: replace winPath with slash
* fix: can't build package on windows * chore: replace winPath with slash
On windows,
fast-globreturn path use '/' as separator, but esbuild use '\', causing the esbuild pluginadd-mjscan't identify client import, so thenextrapackage build output client script as.mjs: