@elevasis/core
v0.74.0
Published
Minimal shared constants across Elevasis monorepo
Readme
@elevasis/core
Shared schemas, types, and constants for building on the Elevasis platform. Published from
packages/core in the Elevasis monorepo, where it is named @repo/core.
Install
pnpm add @elevasis/corePublished surface
The workspace exposes far more subpaths than npm does. publishConfig.exports is the published
surface, and it is these eight:
| Subpath | Contains |
| -------------------------------------- | -------------------------------------------------------------------- |
| @elevasis/core | Alias of ./organization-model — see the note below |
| @elevasis/core/organization-model | The organization model: schemas, defaults, contract IDs |
| @elevasis/core/organization-model/readiness | Readiness snapshot types and helpers |
| @elevasis/core/auth | Multi-tenancy types and the permission catalog |
| @elevasis/core/entities | BaseDealSchema and the other base entity schemas, for extension |
| @elevasis/core/content | Content domain schemas |
| @elevasis/core/knowledge | Knowledge graph types |
| @elevasis/core/test-utils | Test helpers; requires vitest as an optional peer |
Anything else you may see referenced — ./platform, ./execution, ./business/*, ./pdf — is
workspace-internal and does not resolve from an installed copy. Some of those capabilities reach
tenants through @elevasis/sdk instead, which inlines the types it re-exports.
The bare root is an alias, deliberately
@elevasis/core and @elevasis/core/organization-model are the same module. The root entry builds
from src/published.ts, which is one line re-exporting the organization model, so the two .d.ts
files are byte-identical by construction rather than by accident.
This is worth knowing because the workspace root (src/index.ts) advertises a much larger
browser-safe surface that npm does not ship. Import the named subpath you want; the root is kept
only so an existing bare import keeps resolving.
Optional peers
pdfmake is an optional peer, not a dependency. No published subpath reaches the PDF code, so
installing this package does not pull it in. Add it yourself only if you are working inside the
monorepo against @repo/core/pdf.
vitest is likewise an optional peer, needed only by ./test-utils.
License
MIT — see LICENSE.
