chore: keep server private for first alpha - #43
Merged
Conversation
Mark @intent-framework/server as a private workspace package so it is excluded from npm publishing during the first alpha release. - Set private: true in packages/server/package.json - Removed publishConfig from server package - Updated pack:check to filter only 4 publishable packages (core, dom, router, testing) instead of all packages/* - Updated Release-Readiness.md to reflect that server is private and not a first-alpha publishing blocker - Server continues to build and test as part of the workspace
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Mark
@intent-framework/serveras a private workspace package so it is excluded from npm publishing during the first alpha release.Why
The server package should remain in the workspace and continue building/testing, but it should not be publishable in the first alpha. This removes server maturity as a first-alpha publishing blocker.
Changes
private: trueinpackages/server/package.jsonpublishConfigfrom server packagepack:checkto filter only 4 publishable packages (core, dom, router, testing) — no longer runsnpm pack --dry-runon serverdocs/Release-Readiness.mdthroughout:Validation
pnpm test: 310 tests passed (including server tests)pnpm typecheck: cleanpnpm build: all packages build (including server)pnpm lint: cleanpnpm pack:check: 4 packages packed (no server)pnpm dev:web-basic: Vite starts cleanly, HTTP 200@intent/references foundKnown limitations
None.
Follow-up
Remaining first-alpha blockers: