--config cannot point to a package.json
See original GitHub issueCurrently, if a config file is passed explicitly, and that config file is a package.json
, the contents of the package.json
file are loaded instead of a single property within it.
Would it make sense to have a special case for package.json
that calls loadPackageProp
instead?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Error: Cannot read config file: X:\package.json - Stack Overflow
The eslint server is able to run but it could not read the package.json file from the current root folder. Instead it tries...
Read more >package.json has problems with '--config' · Issue #2704 - GitHub
Say I have this file structure: /path/to/project package.json /tmp ... --config cannot point to a package.json davidtheclark/cosmiconfig#79.
Read more >package.json - npm Docs
Files included with the "package.json#files" field cannot be excluded ... The main field is a module ID that is the primary entry point...
Read more >Main property in package.json defines package entry point
First, Node looks for a package.json file and checks if it contains a main property. It will be used to point a file...
Read more >Modules: Packages | Node.js v19.3.0 Documentation
In a package's package.json file, two fields can define entry points for a package: "main" and "exports" . Both fields apply to ...
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 FreeTop 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
Top GitHub Comments
Can do!
@azz Would it be possible for you to make a PR for this change?