Chore/examples latest overrides - #175
Merged
Merged
Conversation
- Replace Object.prototype.hasOwnProperty.call with native Object.hasOwn in worma OpenAPI utils - Fix VS Code extension id generation to use Date.now() - Fix import ordering and adjust publish script order - Add changeset for wormajs and worma-vscode patch releases
- Update docs home components (Cta, Hero) - Sync pnpm workspace and lockfile - Adjust base tsconfig - Remove worm-guidelines directory
🦋 Changeset detectedLatest commit: 247cb81 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
- Add *.tsbuildinfo and tsc_out.txt to .gitignore
eslint-plugin-unicorn@72 relies on Set.prototype.union (Node 22+), so the Node 20 runners crash with 'mapTypes.union is not a function' during lint. Bump the pr and release workflows to Node 22, and tighten engines.node to >=22.0.0 to match the toolchain requirement.
Vitest 4 forwards `new` to a vi.fn()'s implementation, and arrow functions are not constructable. Use `function` expressions for the MultiGeneratorRenderer/MultiProjectRenderer mocks so they can be instantiated with `new` in actions.ts.
The build script used `nr --filter=./packages/* build`, where the unquoted glob was expanded by the CI shell (zsh/bash) instead of being passed literally to pnpm, causing "No matches found" and a broken command. Quote the pattern so pnpm interprets the filter itself.
The e2e job runs under zsh (via xvfb-action), which errors on unmatched globs, unlike bash. Quote the `build:*`/`test:*` patterns in the run-s scripts so the CI shell passes them literally to npm-run-all instead of trying to expand them as file globs.
Add ignoreDeprecations: " 6.0\
Use module/moduleResolution=nodenext instead of the deprecated baseUrl and moduleResolution=node, and add explicit .js extensions to all relative e2e imports. This drops the ignoreDeprecations workaround and makes tsc -p e2e compatible with TypeScript 7.0.
Under module=nodeNext the e2e is still compiled to CommonJS, so Node's native import() of the fixtures.js CJS module exposes module.exports as default, which itself carries the real default export. Unwrap one extra level so export default X resolves to X for both scalar and array fixture declarations.
Merged
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.
No description provided.