-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release next v15.x #2003
Merged
Merged
Release next v15.x #2003
Conversation
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
the latest version of hops dropped node js support in the engines field. this test runs also on 14.x and 13.x branches, which still have node 12 and 15 in their test matrix. if they refer to latest, instead of their own version the test fails as hosp 15 does not support those node versions any more.
hops-release-bot
bot
added
the
📦 v15
Apply this label to a pull request, if it has to be cherry-picked to the v15.x-branch after merging.
label
Oct 27, 2021
To get around the colors dependency in prompt
In case an apollo cache is passed via render options, it was previously not possible to pass `possibleTypes` (aka fragmentTypes.json`) to the cache constructor, because the file was only read in the server mixin. With this change the fragmentTypes.json file is available via a webpack alias as `hops-react-apollo/fragmentTypes.json`, so users can import that file from their application code and pass it to the cache via render options. Additionally this change contains a fix for the cache restoration on the client-side when a custom cache was passed via render options, which would previously not result in the SSR cache state being restored. Co-authored-by: Philipp Hinrichsen <philipp.hinrichsen@new-work.se>
Example: ``` hops-demo:warning Should not import the named export 'config' (imported as 'config') from default-exporting module (only default export is available soon) (../../../../node_modules/something/main.js:8:4-10) hops-demo:warning Critical dependency: the request of a dependency is an expression (./src/main.js:36:0-12) ```
For some reason we see intermittent failures with the source-map-support package (examples: evanw/node-source-map-support#252 and evanw/node-source-map-support#93). The fix that worked for us seems to be to externalize the source-map. Co-authored-by: Markus Wolf <markus.wolf@new-work.se>
ZauberNerd
approved these changes
Jan 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
📦 v15
Apply this label to a pull request, if it has to be cherry-picked to the v15.x-branch after merging.
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.
Next v15.x release
Changes: