Search for a command to run...
As a Senior Principal Engineer at CVSHealth, I specialize in building and optimizing cvs.com to deliver a superior guest experience. Using the latest web technologies, my team and I work diligently to create a user-friendly and intuitive platform that exceeds expectations.
No comments yet. Be the first to comment.
Use the following script to download videos from YouTube using yt-dlp. Incorporating cookies-from-browser can assist in downloading videos that are behind a paywall, provided you have already paid for that content. Please ensure you adhere to the con...
I ran into an issue recently where my autocomplete suggestions on VSCode would only bring up Emmet suggestions and none of the type information would be suggested in autocomplete. After digging through VSCode settings for a bit, figured out that you ...
Intro Setting up a NextJS project is exciting, but securing the localhost environment for testing and development can be challenging. To enable a common usecase of accessing cookies from the production domain (e.g., example.com) while working locally...
This will be a running list of things that I found useful while working on enterprise projects. These can be good tips for other projects too but since there are usually a lot of developers working across enterprise codebases, it is a good idea to es...
I recently set up an Nx monorepo with a lot of sensible defaults. My linting config was working perfect in CI. Running ESLint on terminal through Nx would work fine as well but I was not seeing any ESLint issues on my VSCode editor.
On digging deeper, turns out we need to manually specify the working directories within an Nx monorepo correctly for VSCode to pick up the changes. This is as of Oct 12, 2023.
If you run into a similar issue, the first thing to check would be to
hit Cmd+shift+p
Type ESLint: show output channel and click that option
and make sure you don't see any errors on the terminal that pops up. In my case, the ESLint output channel was complaining about a missing node module within the ESLint flat config. Adding the dependency got rid of that issue.
The next step was to make VSCode aware of the Nx monorepo setup. This can be fixed by opening your VSCode settings.json file. If you're working in a team and need to ensure everyone gets the setup that you do, you can
create .vscode/settings.json file in your Nx monorepo
Add the following config to list each app/package within your monorepo.
{
"eslint.workingDirectories": [
{ "pattern": "./apps/*/" },
{ "pattern": "./packages/*/" }
]
}
Find docs here - https://github.com/microsoft/vscode-eslint#settings-options
After making this change,
hit Cmd+shift+p
Type ESLint: Restart ESLint server and click that option.
That's it! Your Nx monorepos app and package level warnings/errors should now show up within VSCode as you open files. Happy coding!