Skip to content
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.

Feature: Browser-compatible specifier resolution #109

Closed
GeoffreyBooth opened this issue May 20, 2018 · 1 comment
Closed

Feature: Browser-compatible specifier resolution #109

GeoffreyBooth opened this issue May 20, 2018 · 1 comment
Labels

Comments

@GeoffreyBooth
Copy link
Member

I can create a package that imports dependencies and works natively on the web, without needing a build step.

Modules from NPM can be used in my package, without requiring any transpilation or transformation. Tools such as IDEs and linters can understand these dependencies, and all agree on what a specifier means.

Use cases 22, 28, 29.

@ljharb
Copy link
Member

ljharb commented May 20, 2018

I believe package name maps in the browser will make this possible; very much like #107 (comment)

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

No branches or pull requests

2 participants