Skip to content

Conversation

@dbolotin
Copy link
Member

@dbolotin dbolotin commented Jul 6, 2025

No description provided.

dbolotin added 6 commits July 6, 2025 16:04
…f current testing SDK

- Created a comprehensive PRD for the @milaboratories/npm-asset-packer, detailing its purpose, goals, features, and usage.
- Added an overview document for the current Platforma Testing SDK, outlining its architecture, core components, and typical workflows.
- Included desired snippets for testing helpers and smart objects to enhance developer experience.
- Created a new document detailing the architecture and development workflows of the @milaboratories/npm-asset-packer, including its testing strategy and package structure.
- Updated the Product Requirements Document (PRD) for npm-asset-packer to include a comprehensive testing strategy.
- Removed outdated development scripts from the package-builder tool to streamline the build process.
- Introduced a section on configuring Vitest for non-interactive tests to ensure consistency in automated builds and CI/CD pipelines.
- Provided an example configuration for `vitest.config.mts` to disable the interactive "watch" mode.
- Emphasized the importance of not manually editing `CHANGELOG.md` or `package.json` version fields, as Changesets automates these processes.
- Introduced a new section on manually creating changeset files for non-interactive environments.
- Provided an example of the YAML front matter format and how to specify package bump types and change summaries.
- Emphasized that this approach is equivalent to using the interactive `pnpm changeset` command.
- Emphasized the importance of adding new external dependencies to the version catalog in `pnpm-workspace.yaml` before including them in `package.json`.
- Highlighted the practice of centralizing dependency version management to prevent conflicts and maintain consistency across the workspace.
@changeset-bot
Copy link

changeset-bot bot commented Jul 16, 2025

⚠️ No Changeset found

Latest commit: 36eaaea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants