Dependency by url is nice because there doesn't need to be a central repository, but it feels pretty cumbersome to use. URLs are long and hard to remember.
It gets worse if you want to use one dependency in multiple files. You have to copy the url across and upgrading a dependency means searching your entire code base for imports. This is worse than npm, imo
In order to avoid this issue they defined imports maps you can check this video for a more detailed explanation , also the official repo has information about this topic.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Dependency by url is nice because there doesn't need to be a central repository, but it feels pretty cumbersome to use. URLs are long and hard to remember.
It gets worse if you want to use one dependency in multiple files. You have to copy the url across and upgrading a dependency means searching your entire code base for imports. This is worse than npm, imo
In order to avoid this issue they defined imports maps you can check this video for a more detailed explanation , also the official repo has information about this topic.