Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

npm run build all fails #7385

Closed
Pirulax opened this issue Jan 20, 2025 · 0 comments
Closed

npm run build all fails #7385

Pirulax opened this issue Jan 20, 2025 · 0 comments
Labels
Works as intended The behavior described in the issue is intended and is not a bug

Comments

@Pirulax
Copy link

Pirulax commented Jan 20, 2025

I've followed the docs for developing mantine locally from the site here.
But sadly, npm run build all fails with the following message:

$ npm run build all

> [email protected] build
> tsx scripts/build all

[build-all-packages] » Building all packages...
[build-package] » Building package @mantine/hooks
[build-package] » Generating @mantine/hooks *.d.ts files...
[build-package] » ✖  Failed to compile package: @mantine/hooks
[build-package] » ✖  Error:
    at generateDts (C:\git-repos\mantine\scripts\build\generate-dts.ts:6:9)
    exit code: 1
    at EventEmitter.end (C:\git-repos\mantine\node_modules\zx\build\core.cjs:203:26)
    at EventEmitter.emit (node:events:536:35)
    at ChildProcess.<anonymous> (C:\git-repos\mantine\node_modules\zx\build\vendor-core.cjs:494:16)
    at Object.onceWrapper (node:events:639:26)
    at ChildProcess.emit (node:events:524:28)
    at maybeClose (node:internal/child_process:1101:16)
    at ChildProcess._handle.onexit (node:internal/child_process:304:5)

Node: v22.13.0
Yarn: 4.6.0
Mantine: Fresh clone from git

I tried cloning the repo multiple times, didn't help.

@mantinedev mantinedev locked and limited conversation to collaborators Jan 26, 2025
@rtivital rtivital converted this issue into discussion #7412 Jan 26, 2025
@rtivital rtivital added the Works as intended The behavior described in the issue is intended and is not a bug label Jan 26, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Works as intended The behavior described in the issue is intended and is not a bug
Projects
None yet
Development

No branches or pull requests

2 participants