You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work in a monorepo, we use pnpm as package manager.
Recently I try to use vite in a project, but it's buggy.
My project is under //offline/passport/web, when I build //offline/passport/web:dist directly, everything is fine. but if I build it with others, such as build //... , it seems vite got the whole bazel-out directory as build root, it will scan the whole directory to find nodejs modules, but bazel has lots of ephemeral files here, then vite will fail and quit.
I suspect this has causal overlap with aspect-build/rules_esbuild#58. Vite uses ESBuild, and ESBuild is known to follow symlinks out of the Bazel sandbox.
What happened?
I work in a monorepo, we use pnpm as package manager.
Recently I try to use vite in a project, but it's buggy.
My project is under //offline/passport/web, when I build //offline/passport/web:dist directly, everything is fine. but if I build it with others, such as build //... , it seems vite got the whole bazel-out directory as build root, it will scan the whole directory to find nodejs modules, but bazel has lots of ephemeral files here, then vite will fail and quit.
My bazel macro is:
The target is:
Logs here (obviously launch.py is not under //offline/passport and should not be scan by vite):
Version
Development (host) and target OS/architectures:
Ubuntu 20.04
Output of
bazel --version
:5.1.1
Version of the Aspect rules, or other relevant rules from your
WORKSPACE
orMODULE.bazel
file:1.24.0 and 1.26.1 tried both
Language(s) and/or frameworks involved:
JS/JSX, Vite(4.3.1), React 18.2.0
How to reproduce
Any other information?
No response
The text was updated successfully, but these errors were encountered: