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.

Sign up for GitHub

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

Jump to bottom

Implement relative imports #18

Closed
klmr opened this issue May 8, 2014 · 0 comments
Closed

Implement relative imports #18

klmr opened this issue May 8, 2014 · 0 comments
Labels
⚙️ enhancement
Milestone
First final API

Comments

@klmr
Copy link
Owner

klmr commented May 8, 2014

import('./foo') or import('../foo') should not search import.path, and always be relative to the current module’s path.
@klmr klmr added this to the First final API milestone May 8, 2014
@klmr klmr mentioned this issue Jun 16, 2014
Closed
klmr added a commit that referenced this issue Jun 19, 2014
@klmr
Add test for #18 and #24
8a3f337
klmr added a commit that referenced this issue Jun 19, 2014
@klmr
Fix bug in finding the calling module’s path
6807f1c 
Fix a bug in the previous logic whereby a module calling `import` was
not found internally when looking for the module’s path, and the current
working directory was used instead.

Resolves #18 and closes #24.
@klmr klmr closed this as completed in fc89277 Jun 19, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
⚙️ enhancement
Projects
None yet
Milestone
First final API
Development

No branches or pull requests
1 participant
@klmr