Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Requirements should be configured in package.json
See original GitHub issue✖ The --require and -r flags are deprecated. Requirements should be configured in package.json - see documentation.
Is there a particular reason for this?
This pains me:
- I am less flexible now on how to run ava in my project. Unit tests for frontend/backend may have different requirements.
- I kept my
package.jsonclean so far. Now i am forced to put ava fluff in there. - Configuration does not belong in there in the first place IMO.
- CLI-flags can be removed all the way now since i am not going to put ava options in 2 different places.
#1048 looks like api-bikeshed but there is no technical reasoning.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:7 (2 by maintainers)
Top Results From Across the Web
package.json - npm Docs
This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just a...
Read more >Create a package.json File | heynode.com
There are more requirements if you intend to publish the package to the NPM registry to distribute to others. NPM requires a unique...
Read more >The Basics of Package.json explained - Mario Kandut
Hence, when the package gets published the name is required and must be unique on the npm repository. It has requirements to be...
Read more >package.json configuration - Visual Studio - Microsoft Learn
If you are developing a Node.js app with a lot of npm packages, it's not uncommon to run into warnings or errors when...
Read more >How to define the required Node.js version in package.json?
Step 1: Our first and foremost step should be to choose a project on which we are going to work, for example, I...
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
Removing flexibility to a static “one config per package.json” seems pointless to me. You could still have both and the “static (pkg) > overwrites (cli)” model seems more reasonable to me.
2 package.json files as far as i understood.