-
Notifications
You must be signed in to change notification settings - Fork 77
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Another version of escope #127
Comments
By "scopes are split into several files", do you mean it builds a structure which can represent a whole application? That sounds very good to me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I am writing a plugin for webpack to do deep socpe analysis. I modified
escope
and wrapped it into Typescript. just see src/There are several difference:
scopes
are split into several filesImportManager
andExportManager
are added toModuleScope
for tree shaking in webpackexport default function () { ... }
will not be regarded as scope inescope
, but my plugin will analyze itAs an open source project I try to submit PR to
escope
and useescope
directly. There is no need to make a new lib. So I just want to ask willescope
accept these changes. If it's OK, I will submit a PR.The text was updated successfully, but these errors were encountered: