Skip to content

Instantly share code, notes, and snippets.

View Tabrisel's full-sized avatar

Elizaveta Zakharova Tabrisel

View GitHub Profile
@TELEUZI
TELEUZI / components-how-to-en.md
Last active August 17, 2024 09:09

Creating markup with JS

Before reading

Before reading, make sure you are familiar with the following concepts:

  • [DOM]
  • [Functions]
  • [Classes]
  • [OOP]
@TELEUZI
TELEUZI / components-how-to-ru.md
Last active September 3, 2024 18:34

Создание разметки при помощи JS

Перед чтением

Перед чтением убедитесь, что вам знакомы следующие концепции:

  • [DOM]
  • [Functions]
  • [Classes]
  • [OOP]
@nathaniel-miller
nathaniel-miller / linting.md
Created July 7, 2019 03:17
VSCode, ESLint, Prettier, Husky Setup

This is a giant pain in the ass to get working correctly and consistently. Even when it does work, often trying to replicate it in another repository or workspace the setting's don't always seem to work.

I can at times entirely remove my .eslintrcand vscode will still go on its merry way, linting from some mysterious ghost rules. On other occasions things will be great and then, after restarting vscode, I'll be told my imports are invalid (they are not).

As a matter of fact, as I sat down to write this I couldn't get it to linting/format according to my rules. Eventually I reinstalled my node packages with npm install and tried to commit a poorly formatted file (which thankfully failed). That seemed to finally kick something (not sure what) in the pants and linting began to function correctly. But literally, I've spent days getting this sorted out.

Anyway, here's my current setup.

VSCODE SETTINGS

In either ~/.config/Code/User/settings.json or myworkspace.code-workspace: