fix(workspace): allow packages filed to be optional#8969
fix(workspace): allow packages filed to be optional#8969zkochan merged 3 commits intopnpm:pnpm-workspace-configfrom
Conversation
KSXGitHub
left a comment
There was a problem hiding this comment.
There is little reason to use catalogs without a monorepo. The issue's OP wanted to use yaml anchor and alias but pnpm already supports package.yaml.
|
I can't find any instructions in the documentation, could you provide a link to detailed instructions? |
What do you mean? Just write # package.yaml
name: package-name
version: 1.2.3
private: true
dependencies:
foo: 3.2.1And since OP wanted to use yaml anchors: # package.yaml
dependencies:
'@dcloudio/uni-app': &uni-app 3.0.0-alpha-4040520250107001
'@dcloudio/uni-app-harmony': *uni-app
'@dcloudio/uni-app-plus': *uni-app
'@dcloudio/uni-automator': *uni-app
'@dcloudio/uni-cli-shared': *uni-app
'@dcloudio/uni-components': *uni-app
'@dcloudio/uni-h5': *uni-app(the above was copy-pasted from OP's comment) |
|
Thanks for the example, I never knew I could use |
|
I'd like to add the possibility of loading catalogs from configurational dependencies. In that case, it will make sense to have catalogs support in single-package projects. |
Our checking logic can remain as it is, there is no need to modify it? |
close #8968