3 ms·
I've used imports in this manner before and the issue with having a non-centralized place where packages defined has 2 sides: 1. people will import packages wi
by ericlewis 6y ago
I've used imports in this manner before and the issue with having a non-centralized place where packages defined has 2 sides:
1. people will import packages willy-nilly and not think about what they are doing and it becomes harder to understand WHAT they imported (the why becomes more clear imo), I am aware that is very much so JS culture today but I also believe that to be harmful.
2. Having to parse all files to find deps takes time, obviously not a ton of time, but it takes time, it simply doesn't scale appropriately
Working in finance - I think personally that it is really important to make changing the dependency chain something everyone should be VERY aware of.
- diroussel 6y agoRe: point 2 Yes to download each url and walk the tree is going to take time. But it can be cached. Not sure how long it can be cached for. The important thing about url only imports is that it’s a consistent layer to build new tools on top of.