bahmutov / bahmutov/really-need

Overwrite require() in a project but exclude node_modules

Open
#15 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement quality
Dominant language
JavaScript
Stars
107
Forks
4
PR merge metrics
No merged PRs in 30d

Description

I'm thinking about ways one might incorporate [ramda-t](https://github.com/raine/ramda-t) in development process without too much hassle.

One of those I've considered is conditionally overwriting require in non-production environment so that if you `require('ramda')` instead of vanilla Ramda you'd get `ramda-t`.

In order for this to be a feasible approach, the `require` overwrite should only apply to the project's own files.

I know based on the README that `really-need` can be used to overwrite `require` in the way I described, but I also understood that it would apply to global scope and affecting all dependencies as well.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the README's existing description of require overwriting and inspect how really-need applies it to dependencies. Investigate whether the behavior can be limited to the project's own files while excluding node_modules. Done means a documented, feasible approach or an implementation that scopes the overwrite as requested.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.