I discovered module-linker a few weeks ago and was looking how they do linking. As assumed it prefetches all links on startup which is the major difference between OctoLinker and module-linker.

@josephfrazier suggested the same technic a while ago, but I wasn't confidence. Mainly because I was afraid to put that many unnecessary traffic on our service, github and all the registries. In worse case one of them would ban our service. Maybe worth to revisit and investigate into it.

Another major difference is that OctoLinker tries to work specification confirm. For example in NodeJs a require statement can be resolved to many different paths depending on the project structure. require('../foo) can be either ../foo.js or ../foo/index.js. See NodeJS reference for more details. We solve such links as soon as the user requests them. OctoLinker performs some HEAD requests for all the possible locations. Doing that by default for every link would increase significant the traffic produced by OctoLinker, not sure what the consequences would be.

According to the installation count of module-linker, looks like an issue for quite a lot users. I'll investigate into it. Maybe @fiatjaf is willing to help.

Thanks @derimagia for raising attention to this issue on more time.

Show status bar #277

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions