k1-c

📝 Commit Message Policy

This document defines commit message conventions following the Conventional Commits specification with emoji prefixes.

🎯 Basic Format

<emoji> <type>[optional scope]: <description>

[optional body]

bengerman13

Nudge yourself to use Conventional Commits

If you want to use conventional commits, but always forget until it's too late, you can edit your commit template to nudge you to use them

# Please follow the conventional commits specification:
# <type>(<scope>): <subject>
#
# Types:

ef4

Webpack 5 Node Polyfills Upgrade Cheatsheet

Webpack 4 automatically polyfilled many Node APIs in the browser. This was not a great system, because it could lead to surprisingly giant libraries getting pulled into your app by accident, and it gave you no control over the exact versions of the polyfills you were using.

So Webpack 5 removed this functionality. That means you need to make changes if you were relying on those polyfills. This is a quick reference for how to replace the most common patterns.

List of polyfill packages that were used in webpack 4

For each automatically-polyfilled node package name on the left, this shows the name of the NPM package that was used to polyfill it on the right. Under webpack 5 you can manually install these packages and use them via resolve.fallback.

buildmotion

Server Application Setup

• Server Application Setup
  • Tools
  • Create Applications
    • Proxy Configuration
  • Nest Application
  • Build, Test, Serve Application
    • HTTP
• Going Serverless

trungvose

Nx

https://nx.dev/

Nx is a suite of powerful, extensible dev tools to help you architect, test, and build at any scale — integrating seamlessly with modern technologies and libraries while providing a robust CLI, caching, dependency management, and more.

It has first-class support for many frontend and backend technologies, so its documentation comes in multiple flavours.

Principles

rdeak

version: '2.4'

volumes:
  esdata:
    driver: local

networks:
  backend:
    driver: bridge

siakaramalegos

Adding Prettier to a Project

Basic steps for adding Prettier to a project and setting up a pre-commit hook when not using any other linter. Most of these steps can be found in the docs and through other links in the docs.

1. Install prettier:

$ npm install --save-dev --save-exact prettier

2. Create an empty config file to let tools know you're using Prettier:

Zekfad

Quick examples

• feat: new feature
• fix(scope): bug in scope
• feat!: breaking change / feat(scope)!: rework API
• chore(deps): update dependencies

Commit types

• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Changes which doesn't change source code or tests e.g. changes to the build process, auxiliary tools, libraries

colinhacks

// ⚠️ works with Emotion 10 only! ⚠️

// 1. `yarn add emotion-server`
// 2. copy the contents of this file into your `pages` directory
// 3. save it as `_document.tsx`
// should work out of the box



import Document, { Head, Main, NextScript } from 'next/document';

ww9

# Collection of one line text art (◕‿◕✿)

Collection of emojis and one line text art like (╯°□°）╯︵ ┻━┻ 🤗

ּבּ_בּ
טּ_טּ
כּ‗כּ
לּ_לּ
מּ_מּ
סּ_סּ