Results for simonmenke-need

Modern Buffer API polyfill without footguns

Type definitions for the PostHog JavaScript SDK

NodeJS Core Module Extended

EventEmitter3 focuses on performance while maintaining a Node.js AND browser compatible interface.

JS library that allows you to easily serialize and deserialize data with BigInt values

A stand-alone types package for Undici

gRPC Library for Node - pure JS implementation

tiny modular DOM lib for ie9+

A Vite plugin to polyfill Node's Core Modules for browser environments.

Check methods you can use natively without lodash/underscore

Generates and consumes source maps

Vite resolver for TypeScript compilerOptions.paths

ESLint rule to warn against unnecessary React useEffect hooks.

Fix broken node modules with no fuss

utilities for working with typescript's AST

Retry a request.

Enhance ESLint with better support for large scale monorepos

Library for composing asynchronous and event-based operations in JavaScript

A collection of implementation for ECMAScript abstract operations

Cross platform updater for electron applications

Node.js's util module for all engines

Post compiler for Vue template render functions to support ES2015+ features

A simple and reusable datepicker component for React

jetifier from Android Studio, in npm package format

== DESCRIPTION: Need makes ruby relative requires just work. Simply need a file with a relative path and the file will always be required correctly, regardless of what file your application is being launched through. Typically, ruby projects would unshift lib onto $PATH or use the File.dirname(__FILE__) trick. Using need means you don't have to worry about either of these. Assume you have two files, one directly in lib and the other in lib/extensions. Let's assume that file_a in lib requires file_b, in lib/extensions. Previously, you would doing some crazy load path unshifting or use the __FILE__ trick to make these requires flexible enough to work when your app is being accessed by rake, through a test suite, or required as a gem. Now, just use need. In file_a: need{"extensions/file_b"} need "extensions/file_b"