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.
Question: shared types between packages
See original GitHub issueI help maintain the Flow libdefs for react-navigation. For our upcoming 3.0 release, we’re planning on splitting the project into multiple npm packages. We’d ideally be able to define types that are shared across packages only once, but my understanding is that it’s not yet possible to import types between libdefs.
My question is: what is the best practice for this today? Is copy-pasting types between libdefs the only way to do it? If so, does anybody know of a build system that automates/simplifies this process?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:12 (12 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
Initial RFC here Implementation we plan to ship here
We’re just working out the release plan atm as to not break users on current version
@Ashoat I’ve just merged the v4 CLI which is to be published as an alpha initially but the test framework is fully functional and available on the
mainbranch. Feel free to start raising PRs to that branch if you want to try out the new feature.https://github.com/flow-typed/flow-typed/blob/main/CONTRIBUTING.md#importing-types-from-other-libdefs