Michael

For my project being able to use the `node_modules` from the project root (with `noInstall: true` and `includeModules: ...`) would be useful. We're using [patch-package](https://github.com/ds300/patch-package) to patch a few problematic...

I can get around this by enabling the `"source.removeUnusedImports"` code action on format:  But I think there's a race condition between all the code...

I think maybe this is because I'm using a version of ESLint that's `

> @micthiesen did you find any solution to the duplicated imports problem? No I'm back to VSCode 😭

I posted this issue on the Biome extension repo but it looks like it might be an issue with Zed sending the code action (not sure): https://github.com/biomejs/biome-zed/issues/35

Here are my Biome daemon logs in case that's helpful: ~/Library/Caches/dev.biomejs.biome/biome-logs/server.log.2024-07-30-15 ├─ 1ms DEBUG biome_lsp::handlers::analysis Suggested actions: │ [CodeAction(CodeAction { title: "Organize Imports (Biome)", kind: Some(CodeActionKind("source.organizeImports.biome")), diagnostics: None, edit: Some(WorkspaceEdit...

Enabling caching seems to bypass this bug. This is the command we now use: ```bash /kaniko/executor --cache true --cache-ttl 12h --context ${CI_PROJECT_DIR} --dockerfile ${CI_PROJECT_DIR}/${DOCKERFILE_NAME} --destination ${DESTINATION} ```

@tejal29 thanks. I’d like to add that I’ve had inconsistent results trying to reproduce this. I’m uncertain now whether or not it is the caching that fixed things. Good luck...

Somewhat related but is there a way to get rid of the default jest tasks? Not sure where they're coming from tbh:  Also if...