@savvy-web/silk 2.0.0 → 2.1.1

package/packages/silk-effects/dist/dev/pkg/changesets/remark/rules/uncategorized-content.js

@@ -1,31 +0,0 @@
-import { RULE_DOCS } from "../../constants.js";
-import { lintRule } from "../../../../../../../../node_modules/.pnpm/unified-lint-rule@3.0.1/node_modules/unified-lint-rule/lib/index.js";
-
-//#region ../silk-effects/dist/dev/pkg/changesets/remark/rules/uncategorized-content.js
-/**
-* Node types to ignore when detecting uncategorized content (e.g., HTML comments).
-*
-* @internal
-*/
-const IGNORED_TYPES = /* @__PURE__ */ new Set(["html"]);
-/**
-* Determine whether a node is substantive content (not a heading or ignored type).
-*
-* @param node - The AST node to check
-* @returns `true` if the node is content that should be under a heading
-*
-* @internal
-*/
-function isContentNode(node) {
-	if (node.type === "heading") return false;
-	return !IGNORED_TYPES.has(node.type);
-}
-const UncategorizedContentRule = lintRule("remark-lint:changeset-uncategorized-content", (tree, file) => {
-	for (const node of tree.children) {
-		if (node.type === "heading" && node.depth === 2) break;
-		if (isContentNode(node)) file.message(`Content must be placed under a category heading (## heading). Move this content under an appropriate section like "## Features" or "## Bug Fixes". If it doesn't fit an existing category, use "## Other". See: ${RULE_DOCS.CSH004}`, node);
-	}
-});
-
-//#endregion
-export { UncategorizedContentRule };

package/packages/silk-effects/dist/dev/pkg/changesets/schemas/changeset.cjs

@@ -1,148 +0,0 @@
-const require_primitives = require('./primitives.cjs');
-const require_git = require('./git.cjs');
-let effect = require("effect");
-
-//#region ../silk-effects/dist/dev/pkg/changesets/schemas/changeset.js
-/**
-* Effect schemas for changeset entries and dependency updates.
-*
-* @remarks
-* These schemas define the canonical representation of changeset data
-* consumed by the changelog formatter (Layer 2) and validated by the
-* remark-lint pre-validation layer (Layer 1). They enforce constraints
-* such as summary length limits and valid dependency types at system
-* boundaries.
-*
-* @see {@link https://github.com/changesets/changesets | Changesets documentation}
-* @see {@link https://effect.website/docs/schema/introduction | Effect Schema documentation}
-*
-*/
-/**
-* Schema for a changeset summary (1--1000 characters).
-*
-* @remarks
-* Enforces that every changeset has a non-empty summary and caps length
-* at 1000 characters. Longer descriptions should go in the changeset body,
-* not the summary line. Validation messages guide users toward correct usage.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { ChangesetSummarySchema } from "@savvy-web/changesets";
-*
-* // Succeeds — valid summary
-* const summary = Schema.decodeUnknownSync(ChangesetSummarySchema)(
-* 	"Fix authentication timeout in login flow"
-* );
-*
-* // Throws ParseError — empty string
-* Schema.decodeUnknownSync(ChangesetSummarySchema)("");
-* ```
-*
-* @public
-*/
-const ChangesetSummarySchema = effect.Schema.String.pipe(effect.Schema.minLength(1, { message: () => "Changeset summary cannot be empty. Provide a 1-1000 character description of the change (e.g., \"Fix authentication timeout in login flow\")" }), effect.Schema.maxLength(1e3, { message: () => "Changeset summary exceeds the 1000 character limit. Shorten the summary to at most 1000 characters — use the changeset body for additional details" }));
-/**
-* Schema for a changeset object.
-*
-* @remarks
-* Represents a single changeset entry as consumed by the changelog formatter.
-* The `summary` is the human-readable description, `id` is a unique identifier
-* (typically the changeset filename without extension), and `commit` is the
-* optional git SHA that introduced the changeset.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { ChangesetSchema } from "@savvy-web/changesets";
-* import type { Changeset } from "@savvy-web/changesets";
-*
-* const changeset: Changeset = Schema.decodeUnknownSync(ChangesetSchema)({
-* 	summary: "Add retry logic to API client",
-* 	id: "brave-dogs-laugh",
-* 	commit: "a1b2c3d",
-* });
-* ```
-*
-* @see {@link Changeset} for the inferred TypeScript type
-* @see {@link ChangesetSummarySchema} for summary validation rules
-* @see {@link CommitHashSchema} for commit hash format requirements
-*
-* @public
-*/
-const ChangesetSchema = effect.Schema.Struct({
-	/** The changeset summary text. */
-	summary: ChangesetSummarySchema,
-	/** Unique changeset identifier. */
-	id: effect.Schema.String,
-	/** Git commit hash associated with this changeset. */
-	commit: effect.Schema.optional(require_git.CommitHashSchema)
-});
-/**
-* Schema for npm dependency types.
-*
-* @remarks
-* Represents the four standard `package.json` dependency fields using their
-* plural key names as they appear in the manifest. For the singular,
-* table-oriented variant that includes `workspace` and `config` types,
-* see {@link DependencyTableTypeSchema}.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { DependencyTypeSchema } from "@savvy-web/changesets";
-* import type { DependencyType } from "@savvy-web/changesets";
-*
-* const depType: DependencyType = Schema.decodeUnknownSync(DependencyTypeSchema)(
-* 	"devDependencies"
-* );
-* ```
-*
-* @see {@link DependencyTableTypeSchema} for the extended singular-form variant
-*
-* @public
-*/
-const DependencyTypeSchema = effect.Schema.Literal("dependencies", "devDependencies", "peerDependencies", "optionalDependencies");
-/**
-* Schema for a dependency update entry.
-*
-* @remarks
-* Represents a single dependency version change as reported by
-* the Changesets API. Captures the package name, which dependency
-* field it belongs to, and the old and new version strings.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { DependencyUpdateSchema } from "@savvy-web/changesets";
-* import type { DependencyUpdate } from "@savvy-web/changesets";
-*
-* const update: DependencyUpdate = Schema.decodeUnknownSync(DependencyUpdateSchema)({
-* 	name: "effect",
-* 	type: "dependencies",
-* 	oldVersion: "3.18.0",
-* 	newVersion: "3.19.1",
-* });
-* ```
-*
-* @see {@link DependencyUpdate} for the inferred TypeScript type
-* @see {@link DependencyTableRowSchema} for the table-formatted variant
-*
-* @public
-*/
-const DependencyUpdateSchema = effect.Schema.Struct({
-	/** Package name (must be non-empty). */
-	name: require_primitives.NonEmptyString.annotations({ message: () => "Package name cannot be empty" }),
-	/** npm dependency type. */
-	type: DependencyTypeSchema,
-	/** Previous version string. */
-	oldVersion: effect.Schema.String,
-	/** New version string. */
-	newVersion: effect.Schema.String
-});
-
-//#endregion
-exports.ChangesetSchema = ChangesetSchema;
-exports.ChangesetSummarySchema = ChangesetSummarySchema;
-exports.DependencyTypeSchema = DependencyTypeSchema;
-exports.DependencyUpdateSchema = DependencyUpdateSchema;

package/packages/silk-effects/dist/dev/pkg/changesets/schemas/changeset.js

@@ -1,145 +0,0 @@
-import { NonEmptyString } from "./primitives.js";
-import { CommitHashSchema } from "./git.js";
-import { Schema } from "effect";
-
-//#region ../silk-effects/dist/dev/pkg/changesets/schemas/changeset.js
-/**
-* Effect schemas for changeset entries and dependency updates.
-*
-* @remarks
-* These schemas define the canonical representation of changeset data
-* consumed by the changelog formatter (Layer 2) and validated by the
-* remark-lint pre-validation layer (Layer 1). They enforce constraints
-* such as summary length limits and valid dependency types at system
-* boundaries.
-*
-* @see {@link https://github.com/changesets/changesets | Changesets documentation}
-* @see {@link https://effect.website/docs/schema/introduction | Effect Schema documentation}
-*
-*/
-/**
-* Schema for a changeset summary (1--1000 characters).
-*
-* @remarks
-* Enforces that every changeset has a non-empty summary and caps length
-* at 1000 characters. Longer descriptions should go in the changeset body,
-* not the summary line. Validation messages guide users toward correct usage.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { ChangesetSummarySchema } from "@savvy-web/changesets";
-*
-* // Succeeds — valid summary
-* const summary = Schema.decodeUnknownSync(ChangesetSummarySchema)(
-* 	"Fix authentication timeout in login flow"
-* );
-*
-* // Throws ParseError — empty string
-* Schema.decodeUnknownSync(ChangesetSummarySchema)("");
-* ```
-*
-* @public
-*/
-const ChangesetSummarySchema = Schema.String.pipe(Schema.minLength(1, { message: () => "Changeset summary cannot be empty. Provide a 1-1000 character description of the change (e.g., \"Fix authentication timeout in login flow\")" }), Schema.maxLength(1e3, { message: () => "Changeset summary exceeds the 1000 character limit. Shorten the summary to at most 1000 characters — use the changeset body for additional details" }));
-/**
-* Schema for a changeset object.
-*
-* @remarks
-* Represents a single changeset entry as consumed by the changelog formatter.
-* The `summary` is the human-readable description, `id` is a unique identifier
-* (typically the changeset filename without extension), and `commit` is the
-* optional git SHA that introduced the changeset.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { ChangesetSchema } from "@savvy-web/changesets";
-* import type { Changeset } from "@savvy-web/changesets";
-*
-* const changeset: Changeset = Schema.decodeUnknownSync(ChangesetSchema)({
-* 	summary: "Add retry logic to API client",
-* 	id: "brave-dogs-laugh",
-* 	commit: "a1b2c3d",
-* });
-* ```
-*
-* @see {@link Changeset} for the inferred TypeScript type
-* @see {@link ChangesetSummarySchema} for summary validation rules
-* @see {@link CommitHashSchema} for commit hash format requirements
-*
-* @public
-*/
-const ChangesetSchema = Schema.Struct({
-	/** The changeset summary text. */
-	summary: ChangesetSummarySchema,
-	/** Unique changeset identifier. */
-	id: Schema.String,
-	/** Git commit hash associated with this changeset. */
-	commit: Schema.optional(CommitHashSchema)
-});
-/**
-* Schema for npm dependency types.
-*
-* @remarks
-* Represents the four standard `package.json` dependency fields using their
-* plural key names as they appear in the manifest. For the singular,
-* table-oriented variant that includes `workspace` and `config` types,
-* see {@link DependencyTableTypeSchema}.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { DependencyTypeSchema } from "@savvy-web/changesets";
-* import type { DependencyType } from "@savvy-web/changesets";
-*
-* const depType: DependencyType = Schema.decodeUnknownSync(DependencyTypeSchema)(
-* 	"devDependencies"
-* );
-* ```
-*
-* @see {@link DependencyTableTypeSchema} for the extended singular-form variant
-*
-* @public
-*/
-const DependencyTypeSchema = Schema.Literal("dependencies", "devDependencies", "peerDependencies", "optionalDependencies");
-/**
-* Schema for a dependency update entry.
-*
-* @remarks
-* Represents a single dependency version change as reported by
-* the Changesets API. Captures the package name, which dependency
-* field it belongs to, and the old and new version strings.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { DependencyUpdateSchema } from "@savvy-web/changesets";
-* import type { DependencyUpdate } from "@savvy-web/changesets";
-*
-* const update: DependencyUpdate = Schema.decodeUnknownSync(DependencyUpdateSchema)({
-* 	name: "effect",
-* 	type: "dependencies",
-* 	oldVersion: "3.18.0",
-* 	newVersion: "3.19.1",
-* });
-* ```
-*
-* @see {@link DependencyUpdate} for the inferred TypeScript type
-* @see {@link DependencyTableRowSchema} for the table-formatted variant
-*
-* @public
-*/
-const DependencyUpdateSchema = Schema.Struct({
-	/** Package name (must be non-empty). */
-	name: NonEmptyString.annotations({ message: () => "Package name cannot be empty" }),
-	/** npm dependency type. */
-	type: DependencyTypeSchema,
-	/** Previous version string. */
-	oldVersion: Schema.String,
-	/** New version string. */
-	newVersion: Schema.String
-});
-
-//#endregion
-export { ChangesetSchema, ChangesetSummarySchema, DependencyTypeSchema, DependencyUpdateSchema };

package/packages/silk-effects/dist/dev/pkg/changesets/schemas/dependency-table.cjs

@@ -1,203 +0,0 @@
-const require_primitives = require('./primitives.cjs');
-let effect = require("effect");
-
-//#region ../silk-effects/dist/dev/pkg/changesets/schemas/dependency-table.js
-/**
-* Effect schemas for structured dependency table entries.
-*
-* @remarks
-* These schemas define the canonical representation for dependency
-* changes tracked as markdown tables in changeset files and CHANGELOGs.
-* The table format provides a richer view than {@link DependencyUpdateSchema}
-* by supporting singular dependency type names, workspace/config types,
-* and explicit add/update/remove actions.
-*
-* A dependency table row looks like this in a CHANGELOG:
-*
-* | Dependency | Type | Action | From | To |
-* |---|---|---|---|---|
-* | effect | dependency | updated | 3.18.0 | 3.19.1 |
-*
-* @see {@link DependencyUpdateSchema} for the simpler Changesets API format
-* @see {@link https://effect.website/docs/schema/introduction | Effect Schema documentation}
-*
-*/
-/**
-* Valid dependency table actions.
-*
-* @remarks
-* Represents the three possible operations on a dependency: `"added"` for
-* new dependencies, `"updated"` for version changes, and `"removed"` for
-* deletions. Used in the "Action" column of dependency tables.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { DependencyActionSchema } from "@savvy-web/changesets";
-* import type { DependencyAction } from "@savvy-web/changesets";
-*
-* const action: DependencyAction = Schema.decodeUnknownSync(DependencyActionSchema)("updated");
-* ```
-*
-* @public
-*/
-const DependencyActionSchema = effect.Schema.Literal("added", "updated", "removed");
-/**
-* Extended dependency types for table format.
-*
-* @remarks
-* Unlike {@link DependencyTypeSchema} (which uses plural npm field names like
-* `"dependencies"`), this schema uses singular forms (`"dependency"`) and adds
-* two additional types: `"workspace"` for monorepo workspace references and
-* `"config"` for configuration toolchain updates (e.g., ESLint, TypeScript).
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { DependencyTableTypeSchema } from "@savvy-web/changesets";
-* import type { DependencyTableType } from "@savvy-web/changesets";
-*
-* const tableType: DependencyTableType = Schema.decodeUnknownSync(
-* 	DependencyTableTypeSchema
-* )("workspace");
-* ```
-*
-* @see {@link DependencyTypeSchema} for the plural npm-field variant
-*
-* @public
-*/
-const DependencyTableTypeSchema = effect.Schema.Literal("dependency", "devDependency", "peerDependency", "optionalDependency", "workspace", "config");
-/**
-* The canonical accepted-value pattern for a dependency-table From/To cell:
-* the em-dash sentinel (U+2014), a bare/`~`/`^` semver, or — as a last-resort
-* fallback when a `catalog:`/`workspace:` specifier could not be resolved to a
-* concrete version — a pnpm protocol string. Non-overlapping alternatives keep
-* this free of polynomial backtracking (CodeQL).
-*
-* @public
-*/
-const VERSION_RE = /^(\u2014|[~^]?\d+\.\d+\.\d+(?:[-+.][\w.+-]+)?|(?:catalog|workspace|npm|jsr|file|link|portal):[^\s|]+)$/;
-/**
-* Version string or em dash (U+2014) sentinel for added/removed entries.
-*
-* @remarks
-* Accepts either a semver-like version string (with optional `~` or `^`
-* prefix and pre-release/build suffixes) or the em dash character `\u2014`
-* which serves as a sentinel: the "From" column uses `\u2014` for newly
-* added dependencies, and the "To" column uses it for removed ones.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { VersionOrEmptySchema } from "@savvy-web/changesets";
-*
-* // Succeeds — semver version
-* Schema.decodeUnknownSync(VersionOrEmptySchema)("^3.19.1");
-*
-* // Succeeds — em dash sentinel for "no version"
-* Schema.decodeUnknownSync(VersionOrEmptySchema)("\u2014");
-*
-* // Throws ParseError — arbitrary text
-* Schema.decodeUnknownSync(VersionOrEmptySchema)("latest");
-* ```
-*
-* @public
-*/
-const VersionOrEmptySchema = effect.Schema.String.pipe(effect.Schema.pattern(VERSION_RE));
-/**
-* Schema for a single dependency table row.
-*
-* @remarks
-* Represents one row of a dependency update table in a CHANGELOG.
-* Each row captures the dependency name, its type, the change action,
-* and the "from" and "to" version strings. For added dependencies the
-* `from` field is an em dash; for removed dependencies the `to` field
-* is an em dash.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { DependencyTableRowSchema } from "@savvy-web/changesets";
-* import type { DependencyTableRow } from "@savvy-web/changesets";
-*
-* const row: DependencyTableRow = Schema.decodeUnknownSync(DependencyTableRowSchema)({
-* 	dependency: "effect",
-* 	type: "dependency",
-* 	action: "updated",
-* 	from: "3.18.0",
-* 	to: "3.19.1",
-* });
-*
-* // Newly added dependency — "from" is em dash
-* const addedRow: DependencyTableRow = Schema.decodeUnknownSync(DependencyTableRowSchema)({
-* 	dependency: "@effect/cli",
-* 	type: "dependency",
-* 	action: "added",
-* 	from: "\u2014",
-* 	to: "0.50.0",
-* });
-* ```
-*
-* @see {@link DependencyTableRow} for the inferred TypeScript type
-* @see {@link DependencyTableSchema} for a non-empty array of rows
-*
-* @public
-*/
-const DependencyTableRowSchema = effect.Schema.Struct({
-	/** Package or toolchain name. */
-	dependency: require_primitives.NonEmptyString,
-	/** Dependency type. */
-	type: DependencyTableTypeSchema,
-	/** Change action. */
-	action: DependencyActionSchema,
-	/** Previous version (em dash for added). */
-	from: VersionOrEmptySchema,
-	/** New version (em dash for removed). */
-	to: VersionOrEmptySchema
-});
-/**
-* Schema for a dependency table (non-empty array of rows).
-*
-* @remarks
-* Validates that the table contains at least one row. Used to represent
-* the full dependency update table in a changeset or CHANGELOG entry.
-*
-* @example
-* ```typescript
-* import { Schema } from "effect";
-* import { DependencyTableSchema } from "@savvy-web/changesets";
-*
-* const table = Schema.decodeUnknownSync(DependencyTableSchema)([
-* 	{
-* 		dependency: "effect",
-* 		type: "dependency",
-* 		action: "updated",
-* 		from: "3.18.0",
-* 		to: "3.19.1",
-* 	},
-* 	{
-* 		dependency: "typescript",
-* 		type: "config",
-* 		action: "updated",
-* 		from: "5.6.0",
-* 		to: "5.7.2",
-* 	},
-* ]);
-*
-* // Throws ParseError — empty array
-* Schema.decodeUnknownSync(DependencyTableSchema)([]);
-* ```
-*
-* @see {@link DependencyTableRowSchema} for the individual row schema
-*
-* @public
-*/
-const DependencyTableSchema = effect.Schema.Array(DependencyTableRowSchema).pipe(effect.Schema.minItems(1));
-
-//#endregion
-exports.DependencyActionSchema = DependencyActionSchema;
-exports.DependencyTableRowSchema = DependencyTableRowSchema;
-exports.DependencyTableSchema = DependencyTableSchema;
-exports.DependencyTableTypeSchema = DependencyTableTypeSchema;
-exports.VERSION_RE = VERSION_RE;
-exports.VersionOrEmptySchema = VersionOrEmptySchema;