Видео

Since quotes are more of a style/formatting preference, newer versions of ESLint actually have the quotes rule disabled since it was deprecated in version v8.53.0. The prettier-plugin-eslint package enables support for the Prettier rules (including quotes) in ESLint, so you'll see those as errors when running the linter or using any of the IDE extensions. To answer your question, Prettier was intentionally designed to be opinionated, so unfortunately it doesn't provide a way to "disable" the quotes rule. As a workaround, you could ignore that particular file by adding it to a .prettierignore file, but by doing so you'll be ignoring all of the prettier rules and lose the formatting ability for that file. In general, it's not considered a good practice to mix quote styles in a projects codebase, let alone inside of a single file. Would you mind sharing the use case?

Those are examples files I created for this demo video. GitHub pages is designed to host static HTML websites, so you’ll need some basic knowledge of HTML, CSS and GitHub in order to use it effectively. If you are familiar with HTML and CSS, I created another video on how to upload your project to GitHub that might be helpful: ruclips.net/video/TXV8-IX2FXE/видео.htmlsi=r-A68SBX_MN6LL8z Hope that helps!

Thank you! Happy to hear that it was helpful. 🙏

Thank you so much! I'm glad the videos have been helpful. 😊

You're very welcome!

Are you talking about the font? If so, I believe it’s called Virgil, but they also have their own called Excalifont which is pretty similar. Thanks for watching! 🙏

@@thecommoncoder font yes, haha sorry for the typo. Thanks a ton :)

@TechHut Anytime! 😊

That’s awesome! I’m glad the video was helpful. 😊

@@EhsanAfridi For the majority of use cases, you can leave them uninstalled. However, there are certain node packages that are dependent on them that may not work correctly on Windows without them. It ultimately depends on your projects setup, but you can always install them later if you need to.

My pleasure! 🙂

You’re welcome! ☺️

Happy to help! I still get confused myself sometimes. 😜

Thanks! Glad it was helpful. 😊

Which step?

Nice! Glad the video was helpful. 🙂

Thank you! 🙏

@@thecommoncoder your welcome

You're welcome! Glad it helped. 😊

@@francischampagne6469 😂

@@francischampagne6469 I’m going to make a video on Biome soon.

You’re very welcome! ☺️

You should be able to use ESLint at version 8 which supports node 14.x. As far as the peer dependencies, installed packages shouldn’t have a peerDependency on ESLint since that is more of a devDependency (development concern). If it’s complaining about peers from another package, you’ll want to make sure that those are installed in your project, and listed in your “package.json since peers aren’t installed automatically in older versions of node.

That setting is actually under “editor.codeActionsOnSave”, where you would want to set “source.fixAll.eslint” to “true”. The “format on save” setting is helpful when you have a default formatter set up, such as the ones built into VS Code or a 3rd party formatter like Prettier.

@@thecommoncoder Yeah you're right kinda forgot about that.

Have you tried uninstalling/reinstalling the VS Code extension, then restarting VS Code and/or your machine? You might also want to check and make sure you don’t have any other extensions installed that could conflict with ESLint.

You’re welcome! Thanks for watching. 🙏

Glad it was helpful! 😊

It ultimately depends on the project and the team. Some people really don't like the StandardJS defaults, so they'll lean towards something that's more customizable like ESLint or Biome. Thanks for watching!

You're welcome! Glad it was helpful. 🙏

@@IdelsonSilveiraFernandes JSON files aren’t included in the quotes rules for Prettier and ESLint. For JSON in JavaScript files, remember that actual JSON is just a string, so the contents of the string also wouldn’t be included. For working with JSON data, you would use regular JavaScript objects combined with JSON.stringify() and JSON.parse() to convert the data back and forth when needed. Hope that helps!

You're welcome! I'm glad you found it helpful. 😊

Glad it was helpful!

No problem. Hope it helped!

Glad to hear it. Thanks for watching!

You're welcome! I'm glad it was helpful. 😊

Thanks for the suggestion! I'll add that to my list of ideas. The setup for React is essentially the same, but you also need to install the React plugin for ESLint. If you are using the ESLint configuration wizard, just select React when it asks which framework you are using and it will automatically install the plugin for you.

Thanks, I really appreciate it! 🙏

Thanks for the suggestion! I'll have to see if I can change the background color in Excalidraw.

Thanks! Happy to help. 🎉

You're welcome! Hope it was helpful. 😊

Happy to help!

Thanks! Glad you enjoyed it. 🙏

The path module is built into Node, so if you run the eslint configuration wizard and select Node as the environment and JavaScript modules instead of CommonJS, I think you should be good to go. Hope that helps!

It would be nice if there was native linting support in VS Code, but unless you could disable it you’d be giving up a lot of flexibility depending on your workflow. This is especially true on the DevOps side of things, as most CI/CD tooling will run tests/linters as part of the build and deploy jobs. Thanks for watching! 🙏

Thanks for watching! 😊

Hope it was helpful! 🙏

@@JonStaples-c6q There’s no mention of homebrew in the official Node.js docs, which I why I chose to focus on using the installer on both platforms. Having to explain what homebrew is, how to install it, and how to use it is well outside the scope of this video. IMO, it would only add confusion to those looking to get started. That’s about as real and trustworthy as it gets. Thanks for the comment! 😉

Thanks for the sub! Theres definitely more to come. 😊