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
..
index.js	Use swc parse for flight server and client loaders (#33713)	2022-01-27 15:48:09 +00:00
jest-transformer.js	Add support for legacy decorators through tsconfig/jsconfig (#31376)	2021-11-13 18:26:13 +01:00
options.js	Ensure optional chaining in swc matches babel (#33995)	2022-02-04 17:08:01 +00:00