Reasons for slow performance on codespaces

[uetake-ambient]

Select Topic Area

Question

Body

I'm running a project created using Dev Container on codespaces and using prettier and eslint to format files when they are saved, but sometimes the processing speed slows down. What is the reason for this?

[GaurabPrasai]

Hey! This might be happening ESLint is scanning too many files on save. By default it could be checking node_modules or other unnecessary folders try adding a .eslintignore

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[itschanuka]

When you save a file, VS Code may trigger ESLint and Prettier on the whole workspace or multiple files, not just the one you're editing. This becomes slow, especially in Codespaces where resources are limited (CPU/RAM). It’s worse in large projects or if node_modules or dist aren’t ignored.
To fix this, configure your workspace to only lint/format the current file and use .eslintignore / .prettierignore to skip unnecessary folders.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[jfullstackdev]

yes maybe the linter, I also observed it like in SonarLint and connected to SonarQube, it's problematic since it hogs the memory, Codespaces in my uses did never slow down

but this is only temporary like when you re-open the VSCode, after the scanning, it will stabilize and will free resources in local, but problem with Codespaces is, it tends to kill itself after sometime of inactivity, though you can prolong it but that also increase your usage

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬