Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TODO: write down the "resolve a module specifier" algorithm #6

Closed
domenic opened this issue Mar 15, 2018 · 4 comments · Fixed by #133
Closed

TODO: write down the "resolve a module specifier" algorithm #6

domenic opened this issue Mar 15, 2018 · 4 comments · Fixed by #133

Comments

@domenic
Copy link
Collaborator

domenic commented Mar 15, 2018

Preferably including a JS implementation, with at least rudimentary smoke tests.

I've got somewhat of a start on this, and will update this thread as I make progress. Alternately, help would be appreciated if someone else wants to do the work.

@justinfagnani
Copy link
Collaborator

Since we have a pretty good start, is it worth posting that in this issue or a PR for anyone who wants to take it from there?

This was referenced Mar 15, 2018
@domenic
Copy link
Collaborator Author

domenic commented Mar 15, 2018

I don't really trust what we have so far. And I'd like to develop in a much more test-first manner. So I'll avoid doing that for now.

Good discussions to make sure we take into account: #11, #13.

@domenic
Copy link
Collaborator Author

domenic commented Dec 11, 2018

This is largely done in a728303. What remains is scopes and fallbacks. I'll probably leave this open until we have scopes, and then use #18 to track fallbacks.

@domenic
Copy link
Collaborator Author

domenic commented May 13, 2019

602333c added scopes. 8e863b6 added built-in modules. The remaining work is to transcribe into a spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants