Skip to content
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

Tmp .mjs file in the current directory breaks other tools #33

Open
koshic opened this issue Oct 1, 2022 · 0 comments
Open

Tmp .mjs file in the current directory breaks other tools #33

koshic opened this issue Oct 1, 2022 · 0 comments

Comments

@koshic
Copy link

koshic commented Oct 1, 2022

Sometimes I found issues like that during heavy parallel builds (prettier + jest + eslint + tsc + tsup):

build	01-Oct-2022 21:31:04	xxx:lint: 
build	01-Oct-2022 21:31:04	xxx:lint: Oops! Something went wrong! :(
build	01-Oct-2022 21:31:04	xxx:lint: 
build	01-Oct-2022 21:31:04	xxx: ESLint: 8.24.0
build	01-Oct-2022 21:31:04	xxx: 
build	01-Oct-2022 21:31:04	xxx:lint: Error: ENOENT: no such file or directory, open '/home/builder/yyyy/packages/zzzz/tsup.config.bundled_q9ps7cjhg0j.mjs'

Looks like bundle-require creates & immediately removes tsup.config.bundled_q9ps7cjhg0j.mjs in the current dir instead of node_modules/.cache or /tmp/xxx. It's ok for me ('/tsup.config.bundled_*.mjs' in .eslintignore), but may lead to crazy side effects in more complicated scenarios.

condorheroblog added a commit to condorheroblog/vite-plugin-fake-server that referenced this issue Nov 5, 2023
condorheroblog added a commit to condorheroblog/vite-plugin-fake-server that referenced this issue Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant