Consider creating a "top level" package
See original GitHub issueI’m currently building a small app using Evergreen and have found it super tedious to have to keep npm install
ing packages. @stevenmiller888 and I briefly discussed the idea of creating a “top level” package which exports all Evergreen components so this need is removed.
In order to keep our compiled production bundle size reasonable, maybe we also create a Babel plugin to rewrite import { TableCell } from 'evergreen'
to import { TableCell } from 'evergreen-table'
?
Thoughts? @jeroenransijn
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
How to reference to the top-level module in Python inside a ...
This should do the job: top_package = __import__(__name__.split('.')[0]). The trick here is that for every module the __name__ variable ...
Read more >Python beyond top level package error in relative import
In this guide, we're going to discuss what this error means and why it is raised. We'll walk through an example of this...
Read more >pylint false positive attempted relative import beyond top-level ...
python-pylint reports [relative-beyond-top-level] even though I can execute my project just fine. If I use pylint alone in the command line ...
Read more >__main__ — Top-level code environment — Python 3.11 ...
__main__ is the name of the environment where top-level code is run. “Top-level code” is the first user-specified Python module that starts running....
Read more >Chapter 7. Packages - Oracle Help Center
Each immediate subdirectory of this directory would represent a top level package, that is, one whose fully qualified name consists of a single...
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’t we just have a single package like the react-ui-library? It seems to me that this monorepo thing is super over complicating things and I don’t really see the benefits.
With webpack’s tree shaking, bundle size shouldn’t really be an issue with having a single package.