-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: let's use rfr
#104
Comments
@fernandocanizo sounds like a great idea. I like it! How about requirejs? Doesn't it provide a similar feature? |
Here is a little listing of different options to solve the "confusing path names" problem: It concludes with using module-alias - which also has a much better track record and usage in current projects compared to rfr (not actually used) or requirejs (not used anymore) |
And then I have to append that even that is now discouraged and the use of nodejs' native import-mapping (since v14.6.0, v12.19.0) is to be used instead (via ilearnio/module-alias#113 ) Constant change. The only thing to be certain of ;) |
There's a much simpler way to achieve this... add
|
rfr allows to make all requires from the root of the project, reducing the cognitive load by avoiding to have in mind where is a file to realize where a required module lives.
From it's README page:
I offer myself to make such a change should be the idea accepted.
The text was updated successfully, but these errors were encountered: