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
Notes about the dependency upgrades and things to potentially follow up on from #3454.
Replace @reach/router (and current workaround @gatsbyjs/reach-router) with React's router. Reach has a built in older version of React that isn't playing nice with 18.
Remove file-loader dependency (isn't used anymore)
Investigate path-browserify and process usage to see if they are necessary (there should be a better way of getting path and process environment variables). Used in scripts/webpack/webpack.base.config.
Convert cli scripts to typescript for better intellisense/error logging
In scripts/cli/start.js, investigate new syntax for enabling error logging
In scripts/webpack/webpack.client.config, investigate what the replacement for the deprecated stats prop is, and look up compress and why the recommended default is true.
In scripts/webpack/webpack.server.config, investigate null loader usage that was removed for nonvc (we may need an alternative, but the build is currently working without it)
Revisit Monaco usage (React issue is already open?)
Double check asset/resource usage (this replaced the various loader modules) but it looks to be working atm
Validate CSS loading (that we aren't loading it multiple times)
Investigate webpack's included Terser plugin and its usage
Investigate caching and cleaning for the build process - you shouldn't need a yarn clean between builds but the clean isn't properly emptying all the caches
Investigate removing node SSL legacy option from the start script
Notes about the dependency upgrades and things to potentially follow up on from #3454.
Replace
@reach/router(and current workaround@gatsbyjs/reach-router) with React's router. Reach has a built in older version of React that isn't playing nice with 18.Remove
file-loaderdependency (isn't used anymore)Investigate
path-browserifyandprocessusage to see if they are necessary (there should be a better way of getting path and process environment variables). Used inscripts/webpack/webpack.base.config.Convert
cliscripts to typescript for better intellisense/error loggingIn
scripts/cli/start.js, investigate new syntax for enabling error loggingIn
scripts/webpack/webpack.client.config, investigate what the replacement for the deprecatedstatsprop is, and look upcompressand why the recommended default istrue.In
scripts/webpack/webpack.server.config, investigate null loader usage that was removed for nonvc (we may need an alternative, but the build is currently working without it)Revisit Monaco usage (React issue is already open?)
Double check
asset/resourceusage (this replaced the variousloadermodules) but it looks to be working atmValidate CSS loading (that we aren't loading it multiple times)
Investigate webpack's included
Terserplugin and its usageInvestigate caching and cleaning for the build process - you shouldn't need a
yarn cleanbetween builds but the clean isn't properly emptying all the cachesInvestigate removing node SSL legacy option from the start script
Jira Issue: PF-617