vscode-eslint | VSCode extension to integrate eslint into VSCode | Code Analyzer library

As a developer in React.js I highly appreciate the automized help I can get from ESLint on code issues such as unused identifiers.

I have a very small example project in a zip file that I use for experimenting with ESLint.

Even without explicit ESLint rules, Visual Studio Code indicates what identifiers are unused by showing them in a less vibrant color.
In the screenshot below, unUsedArgument and unUsedVariable would have been displayed in about the same color as prevToggle, if they had been used.

App.js in writing :

I'm trying out Github codespaces, specifically the "Node.js & Mongo DB" default settings.

The port is forwarded, and my objective is to connect with MongoDB Compass running on my local machine.

The address forwarded to 27017 is something like https://.githubpreview.dev/

I attempted to use the following connection string, but it did not work in MongoDB compass. It failed with No addresses found at host. I'm actually unsure about how I even determine if MongoDB is actually running in the Github codespace?

I've been using VS coed for some years now and I loved the experience so far, but one of my most recent projects is suddenly slowdowns the VS code drastically, I couldn't figure out why yet. And amazingly other projects do not give me this headache at the moment, with VS code. So I suspect there's something with the particular project I was mentioned before giving me the trouble. I tried deleting the repo and cloning it again in a new place, uninstalled and installed VS code again, but still no luck. It's really laggy, It takes upto a minute or so to update something I wrote in the editor.

Here's the status report of VS code when the problem occurs

I would like to have an application, database and redis service running in a dev container where I'd be able to access my database and redis inside the container, application and on Windows, this is what currently works just as I wanted for my application and database:

.devcontainer.json:

Windows 10 Docker Desktop on WSL2

Goal: serve an angular app from my devcontainer over my local network (specifically for testing on mobile)

Reproduce:

1. Create a hello world angular application in a clean git repo
2. clone the repo into a new devcontainer (Typescript/Node)
3. serve the applcation

Things I've tried (and every permutation herein):

• --network=host (Never worked on windows, but thought it might on WSL2 - doesn't)
• EXPOSE 4200
• runArgs: "-p 4200:4200"
• appPort: [4200]
• opening port 4200 on PC firewall
• ng serve --host 0.0.0.0 --port 4200

Additional Information:

• ng serve does allow me to view the site on my host machine
• cloning the repo to my host and running ng serve --host 0.0.0.0 does allow me to access the site over my network (but moving in and out of the devcontainer isn't reasonable)

My current DockerFile is pretty vanilla:

I'm new to vue and I'm having different errors trying to create new projects with vue create and executing npm run serve.

I've already tried reinstalling node and vue. Changed some PATH, but nothing worked.

First I created the application with:

vue create routing-overview

Then i got this in the final part:

We recently migrated to a monorepo and we are still trying to set everything up. We use typescript and eslint with prettier. The structure is the following:

Everytime I open my project folder in Visual Studio Code, I get an error on the first line of each file. It cannot find my tsconfig.json file because it is looking in the directory I opened VS Code, not where my eslint.json is. I have a functions folder in my root project where the ESLint config is.

Here is part of it:

I have been encountering this error on every single new Next.js project that I create. The page can be compiled without any problem, it just keeps on showing as error on the first line in every js file.

Parsing error: Cannot find module 'next/babel' Require stack:

• D:\app\next_app\ratu-seo\node_modules\next\dist\compiled\babel\bundle.js
• D:\app\next_app\ratu-seo\node_modules\next\dist\compiled\babel\eslint-parser.js
• D:\app\next_app\ratu-seo\node_modules\eslint-config-next\parser.js
• D:\app\next_app\ratu-seo\node_modules@eslint\eslintrc\lib\config-array-factory.js
• D:\app\next_app\ratu-seo\node_modules@eslint\eslintrc\lib\index.js
• D:\app\next_app\ratu-seo\node_modules\eslint\lib\cli-engine\cli-engine.js
• D:\app\next_app\ratu-seo\node_modules\eslint\lib\cli-engine\index.js
• D:\app\next_app\ratu-seo\node_modules\eslint\lib\api.js
• c:\Users\Admin.vscode\extensions\dbaeumer.vscode-eslint-2.1.23\server\out\eslintServer.js