[Feature Request] DRY it up
See original GitHub issueI’d love to see these messages on the package.json
level and not on on every .js
file. Could that be a possible setting?
For people like us on React Native it’s extra important to consider the costs of modules we include. I think the benefit is saving these import costs from ever happening by never bringing in the code at all for modules that can’t pull their weight.
Rationally, it might be an easy feature to switch all that calculating to the source in package.json
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
dry-run" as a comfort feature to "Parameters" · Discussion #2069
[feature request] Add "--dry-run" as a comfort feature to "Parameters" ... users can easily switch on/off without remembering the exact parameter syntax.
Read more >Latest Feature Requests topics - Neural DSP Forum
Topic Replies Views Activity
Read before posting feature requests! 1 1125 March 17, 2021
Assign Splitter in A/B mode to stomp 10 436 December 28,...
Read more >Feature Requests: What are they and how to manage them
Feature requests are a form of product feedback you may frequently encounter as a SaaS product manager. They typically come in the form...
Read more >Feature request: plan with rename - Terraform
I've been working on DRYing up my DNS configuration with a module. That means that the names of all my resources change.
Read more >Feature requests - Kemper Profiler Forum
We are known for frequent feature upgrades. ... Dry/Wet Parameter for Left and Right Stereo Channels ... Ibanez airplane flanger take off mode....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The problem with showing it only at the package.json level is that it ignores the tree shaking aspect of the imports. Maybe we can display the size of the library based on the imports of that library that we found in the project, meaning:
duplicate of #77