You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
8b740fe Thanks @mitchellhamilton! - @preconstruct/next now makes Next.js prefer the module field over the main for server-side bundles. This is different to the behaviour that Next.js provides by default, for that reason, this change is happening in a major release of @preconstruct/next. The module field is generally regarded by most package authors and tools like Preconstruct to only indicate module format and not Node vs browser. This resolves issues with using preconstruct dev with packages that have dependencies that ship Node ESM(in addition to CommonJS).
Configuration
📅 Schedule: "before 7am on Tuesday,before 7am on Wednesday" in timezone Australia/Melbourne.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
If you want to rebase/retry this PR, click this checkbox.
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
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.
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
This PR contains the following updates:
^3.0.1->^4.0.0Release Notes
preconstruct/preconstruct
v4.0.0Compare Source
Major Changes
8b740feThanks @mitchellhamilton! -@preconstruct/nextnow makes Next.js prefer themodulefield over themainfor server-side bundles. This is different to the behaviour that Next.js provides by default, for that reason, this change is happening in a major release of@preconstruct/next. Themodulefield is generally regarded by most package authors and tools like Preconstruct to only indicate module format and not Node vs browser. This resolves issues with usingpreconstruct devwith packages that have dependencies that ship Node ESM(in addition to CommonJS).Configuration
📅 Schedule: "before 7am on Tuesday,before 7am on Wednesday" in timezone Australia/Melbourne.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.