-
Notifications
You must be signed in to change notification settings - Fork 569
Extract js package to another repo #919
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
Comments
This is a reasonable feature request to consider. It should be possible to accomplish this, but it would take a fair bit of implementation work (which is hard due to #894). It also has the downside of potentially creating churn (people updating As an alternative, have you considered using the |
|
(I will leave this issue open for some time, ok?) |
Probably |
Currently, while GopherJS API is presented in the package js (https://github.com/gopherjs/gopherjs/tree/master/js). And to use it every user needs to check out a quite heavy
github.com/gopherjs/gopherjs
repo.I'm proposing to extract
js
package to a new repo (probablygithub.com/gopherjs/js
) and alias its types ingithub.com/gopherjs/gopherjs/js
.The back compatibility will be safe, users will use(depend) on a much smaller package, we can introduce Go modules to the new package with out any problems(hopefully).
I hope I'm not missing something and it's possible to make. Thank you.
UPD: aliases were added in 1.9, I'm not sure what is the minimal supported version for gopherjs.
The text was updated successfully, but these errors were encountered: