codfish

My personal & professional linting setup for JS projects.

• Modern ESLint v9+ flat config: Uses the new flat configuration format
• Dynamic feature detection: Automatically configures based on your project's dependencies
• TypeScript support: Full TypeScript linting with modern typescript-eslint parser and rules
• React ecosystem: React, React Hooks, and JSX accessibility rules when React is detected
• Next.js support: Automatically configures Next.js official plugin linting rules when detected
• Test framework agnostic: Supports Jest and Vitest with automatic detection
• Testing Library integration: Automatically includes Testing Library rules for test files
• YAML/YML support: Built-in linting for YAML configuration files

elijahmanor

{
  "extends": ["react-app", "plugin:prettier/recommended"]
}

greyscaled

Sequelize + Express Starter Guide

Based off of: http://docs.sequelizejs.com/en/1.7.0/articles/express/

Create your project directory

Create and initialize your a directory for your Express application.

$ mkdir sequelize-demo

deepal

r = uv__loop_alive(loop);
  if (!r)
    uv__update_time(loop);

while (r != 0 && loop->stop_flag == 0) {
    uv__update_time(loop);
    uv__run_timers(loop);
    ran_pending = uv__run_pending(loop);
    uv__run_idle(loop);
    uv__run_prepare(loop);

ledmaster

nkbt

[push]
  default = current
[user]
  email = [email protected]
  name = Nik Butenko
[core]
  autocrlf = input
  excludesfile = /Users/nkbt/.gitignore
  ignorecase = true
[alias]

nkbt

{
  "env": {
    "browser": true,
    "node": true,
    "es6": true
  },

  "plugins": ["react"],

  "ecmaFeatures": {

vincentbernat

'use strict';

var setup = require('../.'),
    should = require('should'),
    path = require('path'),
    Sequelize = require('sequelize'),
    db = require('../../lib/db'),
    config = require('../../lib/config'),
    logger = require('../../lib/logger');

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions