Open sgraband opened 12 months ago
While updating the CDT Cloud blueprint to the latest version of this extension i noticed that some dependencies do not seem to be provided correctly.
To be more specific: It seems like these dependencies from the root package.json are only references as dependencies there, but not in the
theia-traceviewer
extensionspackage.json
.Therefore, i need to manually add these dependencies to my project, when i want to consume the
theia-traceviewer
extension.These dependencies should probably be added as peer dependencies in the
theia-traceviewer package.json
. Or was there a specifiic reason for it to be implemented this way?
No, I don't think there was a specific reason for that. When the change was introduced I think it was not noticed or not questioned. If you think that's incorrect, could you please provide a PR and we will review it.
Thanks for bringing this up.
I believe that this is a legit issue - the way these production dependencies are defined ATM, they will be available to the test application but not be included in the published Theia extension. If they are only needed in the extension, I think they should be moved there.
The two related @types
dependencies [1] should probably be moved to the extension too, in devDependencies
.
While updating the CDT Cloud blueprint to the latest version of this extension i noticed that some dependencies do not seem to be provided correctly.
To be more specific: It seems like these dependencies from the root package.json are only references as dependencies there, but not in the
theia-traceviewer
extensionspackage.json
.Therefore, i need to manually add these dependencies to my project, when i want to consume the
theia-traceviewer
extension.These dependencies should probably be added as peer dependencies in the
theia-traceviewer package.json
. Or was there a specifiic reason for it to be implemented this way?