Skip to content

Instantly share code, notes, and snippets.

View SwapnilSoni1999's full-sized avatar
👨‍💻
SGFoYSEgWW91IGRlY29kZWQgaXQuIGxldHMgY29ubmVjdC4K

Swapnil Soni SwapnilSoni1999

👨‍💻
SGFoYSEgWW91IGRlY29kZWQgaXQuIGxldHMgY29ubmVjdC4K
View GitHub Profile
@mvaisakh
mvaisakh / Bringup.md
Last active October 22, 2025 16:50
An Android Device Tree Bringup Guide

A small Device Tree Bringup Guide

Introduction

So, you guys might be wondering, how do these "Developers" get your favourite Custom roms, such as LineageOS, Paranoid Android etc., to their own devices. Well I'm here to Guide you on how to do it, specifically on how to bringup or make your own device tree from scratch or adapting.

Gist of this Guide: This is for people with genuine interest in Android OS porting/development. After going through this guide, you should be able to do a total device tree bringup on your own.

Prerequisite: Certain requirements are to be met before you start with this amazing journey.

@frozenpandaman
frozenpandaman / widevine-decryption.md
Last active November 1, 2025 15:39
download videos protected with widevine DRM
@kkoyung
kkoyung / widevine-decryption.md
Created May 26, 2024 05:33 — forked from frozenpandaman/widevine-decryption.md
download videos protected with widevine DRM
@m3h3d1ha2an
m3h3d1ha2an / property-user-does-not-exist-on-type-requestparamsdictionary-any-any-parsedqs-recordstring-any.md
Last active March 30, 2025 23:44
Problem: Property 'user' does not exist on type 'Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>'

Problem: Property 'user' does not exist on type 'Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>'

When working with Express and jsonwebtoken, it's better to use res.locals to store user-related data rather than modifying the req object directly. This approach adheres to best practices and avoids potential issues with modifying the req object.

Here’s why:

  1. Separation of Concerns: res.locals is designed for passing data to subsequent middleware or templates. It keeps the request object clean and unmodified.
  2. Middleware-Safe: Using res.locals ensures that the data is available to other middleware without interfering with the original request object.

Instead of: