Skip to content

V3: Migrate away from @zowe/cli to @zowe/*-for-zowe-sdk packages #2719

@zFernand0

Description

@zFernand0

Is your feature request related to a problem? Please describe.

We should leverage the full capabilities of the Node.js SDK without importing functionality directly from the CLI package. In addition to that, the @zowe/cli package comes with an npm-shrinkwrap.json file which makes sense for the CLI. However, this may indicate that we have to wait for the CLI to release a new update before Zowe Explorer can fix any transitive dependencies.

Describe the solution you'd like

Instead of @zowe/cli, to import:

  • @zowe/zos-files-for-zowe-sdk for data set and USS operations
  • @zowe/core-for-zowe-sdk for any configuration related matters across Zowe Explorer
  • @zowe/zos-tso-for-zowe-sdk for TSO related operations
  • ...and others

Describe alternatives you've considered

To continue with the CLI dependency, which has the an npm-shrinkwrap. This can force us to use yarn.resolutions or pnpm.overrides if we have to update some transitive dependency, but this can have negative effects (luckily none so far)

Additional context

This was discussed during the extended ZE standup on Feb 13th, 2024

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestpriority-highProduction outage - this quarter or at least next quarterv3

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions