How are the Manifest
types used in the PNPM internals (high level overview)?
#8139
Unanswered
lancejpollard
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I see in @pnpm/types there are these 4 manifest types:
BaseManifest
DependencyManifest
ProjectManifest
PackageManifest
What exactly do you mean by "manifest"? What are the differences between these 4 types of manifests? Is the
PackageManifest
equal to thepackage.json
, or is it slightly different? That's basically what I'm trying to wrap my head around, what purpose these manifests serve and how they relate to thepackage.json
.The
BaseManifest
type looks like this, and looks very close to the package.json, yet there are fields which I haven't really seen in the package.json, so I'm wondering if it is a mixup of different concepts I'm unaware of?For example, I just learned that the package.json has
typesVersions
andexports
fields (among others here), but it doesn't seem to havetypings
or maybe it does have all these fields?Also, what is the need for creating multiple types of manifest if they are just representations of the package.json? Could one manifest type suffice, or what am I missing?
Thank you so much for all your help in these questions!
Beta Was this translation helpful? Give feedback.
All reactions