Nested packageProp path
See original GitHub issueUsing cosmiconfig
in a yarn version tool, yvm
. It would be helpful to be able to use the yarn version in the package.json engines prop as a search place for configuration. e.g.
packageProp: 'engines.yarn',
A custom loader would probably work, but it seemed like a useful native feature regardless.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
nested-prop-paths - npm
nested-prop-paths. Use when you don't know path to a key/prop. Finds null value prop. Returns all paths, then we can filter the path...
Read more >How to denormalize nested list in R? - Stack Overflow
I'd like to find a clean and readable way to convert a structure like src (parsed from JSON, that's why there are a...
Read more >yvolohov/prop-extractor: Get values from complicated data ... - GitHub
Get values from complicated data structures, nested arrays and objects, using request string like 'foo.[].bar.[].baz'. www.npmjs.com/package/prop-extractor.
Read more >prop-extractor - npm Package Health Analysis | Snyk
Get values from complicated data structures, nested arrays and objects, ... The npm package prop-extractor receives a total of 1 downloads a week....
Read more >ScalaTest 3.0.8 - org.scalatest.path - javadoc.io
Using a path class, you can make a statement in text, then implement that statement in code (including mutating state), and nest and...
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
@davidtheclark I can put up a PR with this change, already have most of the code running locally.
Yeah, I think this is something we should support, @iamogbz. Since this is the first request related to a custom
package.json
loader, I think I’m in favor of supporting dot notation (as @iamogbz suggests) instead of allowing people to specify custompackage.json
loaders — which seems like a more significant change, and I’m having a hard time thinking of what people might do other than the equivalent of dot notation.