require and resolve modules relative to a path of your choice
TypeScript definitions for require-relative
Little helper to make node.js require relative to your project root
require relative to your root project
browserify transform for require-relative-main
require relative to your project root.
require relative to your project root.
require relative to your project root.
Use the relative color syntax in CSS
Easily get the CWD (current working directory) of a project based on package.json, optionally starting from a given path. (node.js/javascript util)
Returns `true` if the path appears to be relative.
Memoize the results of the path.relative function
Utility function to load nyc configuration
"It manages all the require relative paths from one centralized pathsLocation.json file"
require a module relative to the 'main' script
Tiny function that provides relative, human-readable dates.
Resolve relative IRIs to absolute IRIs given a base IRI
Implements performance.now (based on process.hrtime).
utils for webpack loaders
Check if a URL is relative
gets the package name for a require statement
Parse the things that can be arguments to `npm install`
Get the relative filepath from path A to path B. Calculates from file-to-directory, file-to-file, directory-to-file, and directory-to-directory.
Webpack loader that resolves relative paths in url() statements based on the original source file
In Ruby 1.9.2, "." was removed from $:. This is a good idea, for security reasons. This gem backports this to Ruby 1.8.
Ruby 1.9's require_relative for Rubinius and MRI 1.8. We also add abs_path which is like __FILE__ but __FILE__ can be fooled by a sneaky "chdir" while abs_path can't. If you are running on Ruby 1.9 or greater, require_relative is the pre-defined version. The benefit we provide in this situation by this package is the ability to write the same require_relative sequence in Rubinius 1.8 and Ruby 1.9.
This module changes the meaning of relative requires from "relative to the current pwd" to "relative to the requiring file". By just changing this little thing, it lets you remove lots of uglyness regarding $LOAD_PATH
Sometimes it causes some trouble. Take that as read. This will let you know when you slip, and include require_relative.
Fixes require_relative in Pry.
Basic utility to require a directory.
Relative require, relative autoload and __DIR__
Easy way to require multiple files from a relative path
This is a plugin for converting urls in markdown files to relative paths required by Jekyll.
require all files in given relative path!
Allows files to be required relative to the current file. Like, require '../lib/my_file' Which serves as a replacement for the tired idiom of, require File.join(File.dirname(__FILE__), '..', 'lib', 'my_file') Ruby's built-in require still works the same require 'test/unit'
== 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"
No description provided.
No description provided.