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.
Readme examples use package.json config even though it's deprecated
See original GitHub issueType of Issue
[x] Bug Report
[ ] Feature Request
Description
The Readme for this repo doesn’t explain that config via package.json (as opposed to ng-package.json) is deprecated and uses the former in its examples.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:5 (2 by maintainers)
Top Results From Across the Web
package.json - npm Docs
Description. This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just...
Read more >Configuration Files - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >Will npm try to avoid installing a deprecated package version?
I tested and confirmed that it does indeed ignore deprecated versions if there is another version it can use. (I temporarily deprecated ......
Read more >Options - TypeDoc
When TypeDoc loads a tsconfig.json file, it also will read TypeDoc options declared ... In configuration files, this option accepts an array of...
Read more >Specifics of npm's package.json handling - manpages.ubuntu!
If a dependency can be used, but you would like npm to proceed if it cannot be found or fails to install, then...
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
Hmm, yeah that article isn’t quite accurate 😦
In the future it is likely that the nested
package.jsonfiles will disappear, as we’d be able to leverage package exports. Those have already been adopted in the APF 13 format (see@angular/coreas an example) but the nestedpackage.jsonfiles are still present today as export fields are not universally supported by tooling yet.This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
This action has been performed automatically by a bot.