-
Notifications
You must be signed in to change notification settings - Fork 12
chore: upgrade angular@19 versions #250
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
Conversation
✅ Deploy Preview for plugin-angular-universal-demo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
dc9e3a7
to
99ee34c
Compare
…ndencies are updated
const excludedPathsWithMaskedHashes = config.excludedPath.map((path) => path.replace(/-[A-Z\d]{8}\./, '-HASHHASH.')) | ||
|
||
assert.deepEqual(excludedPathsWithMaskedHashes, [ | ||
'/.netlify/*', | ||
'/favicon.ico', | ||
'/heroes/index.html', | ||
'/index.csr.html', | ||
'/main-KVCR6MBP.js', | ||
'/polyfills-FFHMD2TL.js', | ||
'/styles-5INURTSO.css', | ||
'/main-HASHHASH.js', | ||
'/polyfills-HASHHASH.js', | ||
'/styles-HASHHASH.css', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
checking concrete hashes here is causing problems so instead I do mask hash to ensure to still be able to ensure that expected static assets are produced and excluded from function configuration so we don't have to update assertions with each Angular version bump
New revision of #227
Fixes https://linear.app/netlify/issue/FRB-1622/possible-regression-with-new-framework-release