Simplify import
See original GitHub issueWe are planning to simplify the way components are imported in v4. Currently, there are multiple ways to import components depending on the usage. We would like to change that in v4: there will only be one entry point for all components:
import { Button, Container, Table } from 'react-bulma-components';
This makes the TypeScript definition file simpler and importing components much less tedious.
cc @couds are we settled on this? If so, I will start making this change.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Simplify - SymPy 1.11 documentation
A dictionary that can be sent to subs to restore eq to its original symbols is also returned. >>> from sympy import posify,...
Read more >5 Tips for Simplifying the Process of Importing - Eezyimport
Before your international shipment can enter US soil, it must first pass through the US Customs Border Protection Bureau (CBP). Going through custom...
Read more >How to simplify and organize imports in Typescript
We can simplify it by exposing all files, from a single file, to point to all of them. Create drinks.ts into the service...
Read more >python 3.x - How to simplify my imports - Stack Overflow
This is just a example. In my project (not finished), I have 21 classes and two packages. – Mauricio. Feb 28, 2015 at...
Read more >Angular simplify Typescript imports | Gaetan Redin - Medium
Simplify TypeScript import Hey, I'm sure you have already done something like: import { MyService } from '../../../../../core/services/my-service. service'; Um ...
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
I actually prefer the namespaced import because it makes it clear semantically that the component is part of a
Form
.Tree shaking should be working (tested with CRA only). Would be great if someone can confirm this with other configurations by installing the next branch of this library:
For some reason, when trying to install next branch with yarn, yarn also resolves devDependencies, which drastically increases the number of dependencies installed. Not sure if this is a problem with yarn itself or if it’s our fault.
cc @timorthi @couds