JJ Kasper a65e3612d0 Ensure optional chaining in swc matches babel (#33995) ... This ensures we always transpile optional chaining and nullish coalescing with swc the same as we do [with babel](4812e22992/packages/next/build/babel/preset.ts (L97-L98)) since it can cause issues with webpack even when the node target supports these features. The specific case this seems to cause issues with webpack is when a value is imported and optional chaining is used on the import value webpack is stripping the optional chaining cc @sokra ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` Fixes: https://github.com/vercel/next.js/issues/33915		2022-02-04 17:08:01 +00:00
..
components	Fix dynamic css unloading (#17173)	2020-11-03 05:23:31 +00:00
pages	Ensure optional chaining in swc matches babel (#33995)	2022-02-04 17:08:01 +00:00
public	Add CSP to Image Optimization API (#28620)	2021-08-30 16:51:47 +00:00
static/data	Fix the route redirect error when we've multiple path params. (#2652)	2017-07-26 22:31:49 +05:30
test	Update to filter loader specific files from traces (#32267)	2021-12-14 10:41:10 -06:00
info.json	Use our static file rendering machanism to serve pages.	2018-01-13 10:36:50 +05:30
next.config.js	Move outputFileTracing config up (#30295)	2021-10-25 23:22:45 -05:00