You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm thinking about ways one might incorporate 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.
The text was updated successfully, but these errors were encountered:
I'm thinking about ways one might incorporate 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 getramda-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 overwriterequire
in the way I described, but I also understood that it would apply to global scope and affecting all dependencies as well.The text was updated successfully, but these errors were encountered: