-
Notifications
You must be signed in to change notification settings - Fork 102
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
Fixed Component manager exportation #2380
Conversation
Signed-off-by: Seb Julliand <sjulliand@arcadsoftware.com>
Signed-off-by: Seb Julliand <sjulliand@arcadsoftware.com>
Signed-off-by: Seb Julliand <sjulliand@arcadsoftware.com>
Signed-off-by: Seb Julliand <sjulliand@arcadsoftware.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see my only comment, and other than that, it's all good.
Signed-off-by: Seb Julliand <sebjulliand@gmail.com>
Signed-off-by: Seb Julliand <sebjulliand@gmail.com>
Thanks @worksofliam ! |
👋 A new build is available for this PR based on d19e868. |
Please see my alternative PR: #2381 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like components are still loading good and the test cases are passing. Merge away!
Changes
The Component Manager could not be used by other extensions because of the way types were exported.
This PR fixes this, allowing other extension to actually contribute components to Code for i.
It also adds an
.npmrc
file to avoid issues whennpm
is ran with a proxy npm repo defined locally.How to test this PR
Checklist