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.
[Opinion] Component's package.json?
See original GitHub issueWhy a package.json under components?
I’m coming new to this after seeing a ton of React projects, this is the first time I encounter this approach, and IMHO it’s counterintuitive. I took a look at the file thinking this was some weird black magic to make components exportable (maybe Lerna/monorepo related or something) until I read what was about.
I’d prefer a rename of the actual component to index.js to achieve the same effect. Granted, this breaks the naming convention for that particular file, but it’s less counter-intuitive and more common.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@dolbyzerr You can easily hack scaffold too 😉
@blackxored Sounds good in theory but in practice would be horrible. Think about all of your component files open in your IDE, all the files at the top of your screen would say index.js… which one do you click on? Which one is the one you want?
Other reasons aside, would be a terrible developer experience.