Skip to content

Conversation

@AtofStryker
Copy link
Contributor

@AtofStryker AtofStryker commented Oct 24, 2025

  • Closes

Additional details

Cleans up some of the migrated packages to

  • make sure they ship with declaration types as opposed to referencing the source directory for types
  • Also adds watchers for frequently developed packages
  • uses tsconfig.json instead of tsconfig.base.json for better IDE typescript support

Steps to test

How has the user experience changed?

PR Tasks


Note

Standardizes TS configs to emit declaration files, points package types to built outputs, adds watch scripts, and replaces lazy fs-extra require with direct import in resolve-dist.

  • Build/Type Declarations:
    • Enable "declaration": true and point "types" to built outputs (cjs/index.d.ts) in @packages/config, @packages/errors, @packages/resolve-dist, @packages/scaffold-config, @packages/types.
    • Switch tsconfig.*.json to extend tsconfig.json across packages (config, errors, icons, network-tools, network, resolve-dist, scaffold-config, telemetry, types).
  • Developer Experience:
    • Add watch scripts (parallel CJS/ESM builds) to config, errors, scaffold-config, types; enhance telemetry watch to include browser build.
    • packages/root/README.md: note about manually retriggering build (no watcher).
  • Code:
    • packages/resolve-dist/lib/index.ts: replace lazy require('fs-extra') with direct import fs from 'fs-extra'.

Written by Cursor Bugbot for commit 229ae60. This will update automatically on new commits. Configure here.

…se tsconfig.json instead of tsconfig.base as it has better IDE support. Also add a watcher
…se tsconfig.json instead of tsconfig.base as it has better IDE support. Also add a watcher
…se tsconfig.json instead of tsconfig.base as it has better IDE support. Also add a watcher
…se tsconfig.json instead of tsconfig.base as it has better IDE support. Also add a watcher
…se tsconfig.json instead of tsconfig.base as it has better IDE support. Also add a watcher
…se tsconfig.json instead of tsconfig.base as it has better IDE support. Also add a watcher
…se tsconfig.json instead of tsconfig.base as it has better IDE support. Also add a watcher
…se tsconfig.json instead of tsconfig.base as it has better IDE support. Also add a watcher
…se tsconfig.json instead of tsconfig.base as it has better IDE support. Also add a watcher
@AtofStryker AtofStryker self-assigned this Oct 24, 2025
@AtofStryker AtofStryker changed the title Chore/clean up migrated packages chore: unify migrated packages Oct 24, 2025
@cypress
Copy link

cypress bot commented Oct 24, 2025

cypress    Run #66817

Run Properties:  status check passed Passed #66817  •  git commit 229ae60bec: use declarations instead of src root and ship it with package. also use tsconfig...
Project cypress
Branch Review chore/clean-up-migrated-packages
Run status status check passed Passed #66817
Run duration 19m 47s
Commit git commit 229ae60bec: use declarations instead of src root and ship it with package. also use tsconfig...
Committer Bill Glesias
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 13
Tests that did not run due to a developer annotating a test with .skip  Pending 1102
Tests that did not run due to a failure in a mocha hook  Skipped 4
Tests that passed  Passing 26755
View all changes introduced in this branch ↗︎

Warning

Partial Report: The results for the Application Quality reports may be incomplete.

UI Coverage  46.02%
  Untested elements 185  
  Tested elements 162  
Accessibility  97.98%
  Failed rules  4 critical   8 serious   2 moderate   2 minor
  Failed elements 101  

Copy link
Member

@jennifer-shehane jennifer-shehane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one comment

"test-unit": "vitest run",
"tslint": "tslint --config ../ts/tslint.json --project .",
"watch": "tsc --watch"
"watch": "yarn build:cjs --watch & yarn build:esm --watch & yarn build:browser -w"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AtofStryker Maybe not relevant to this PR, but I do see these warnings running this watch:

(!) Unresolved dependencies
https://rollupjs.org/troubleshooting/#warning-treating-module-as-external-dependency
@opentelemetry/sdk-trace-web (imported by "src/client.ts")
@opentelemetry/resources (imported by "src/client.ts" and "src/telemetry/index.ts")
@opentelemetry/sdk-trace-base (imported by "src/client.ts" and "src/processors/on-start-span-processor.ts")
@opentelemetry/api (imported by "src/span-exporters/websocket-span-exporter.ts" and "src/telemetry/index.ts")
@opentelemetry/exporter-trace-otlp-http (imported by "src/span-exporters/websocket-span-exporter.ts")
@opentelemetry/semantic-conventions (imported by "src/telemetry/index.ts")
@opentelemetry/core (imported by "src/span-exporters/console-trace-link-exporter.ts")

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is due to rollup not actually bundling the node_modules inside the browser version of the telemetry package, which is expected currently. At least for now, we likely want to keep the warnings present since it describes the behavior

@AtofStryker AtofStryker merged commit d5cc26d into develop Oct 28, 2025
87 of 96 checks passed
@AtofStryker AtofStryker deleted the chore/clean-up-migrated-packages branch October 28, 2025 00:07
@cypress-bot
Copy link
Contributor

cypress-bot bot commented Nov 4, 2025

Released in 15.6.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v15.6.0, please open a new issue.

@cypress-bot cypress-bot bot locked as resolved and limited conversation to collaborators Nov 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants