chore: add pnpm workspace configuration to allow builds#120
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Changed imports in theme provider to use type imports for ThemeProviderProps. - Updated JSON documents to streamline heading formatting. - Refactored content script to use node:fs and node:path for consistency. - Adjusted imports in settings and types to utilize type imports for better clarity.
…ental corepack environment variable
…npm workspace configuration
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.
This pull request primarily updates project dependencies to their latest patch versions and introduces a new configuration to the
pnpm-workspace.yamlfile. These changes help ensure the project remains up-to-date with bug fixes, security updates, and compatibility improvements.Dependency updates:
package.json, includingnext,react,react-dom,@next/third-parties,@tailwindcss/postcss, as well as development dependencies like@biomejs/biome,@types/node,postcss,tailwindcss, andtypescript-eslint, to their latest patch versions. This helps maintain compatibility and brings in the latest fixes and enhancements. [1] [2]Build configuration:
allowBuildsconfiguration foresbuildandsharpinpnpm-workspace.yamlto explicitly allow these packages to be built, which can help with workspace build consistency and troubleshooting.