Repository navigation
__webpack_require__(...).context is not a function #8
Description
From swc-project/swc-loader#64 (comment) by Gio (@callmeteus)
I'm trying to port from babel-loader and ts-loader to swc-loader, but everytime
require.contextis called, it returns undefined.When printing the
requirevariable, it returns the following module:function webpackEmptyContext(req) { var e = new Error("Cannot find module '" + req + "'"); e.code = 'MODULE_NOT_FOUND'; throw e; } webpackEmptyContext.keys = () => ([]); webpackEmptyContext.resolve = webpackEmptyContext; webpackEmptyContext.id = 5102; module.exports = webpackEmptyContext;
Activity
thatsmydoing commentedon Oct 27, 2023
The issue we've found here is when the regexp passed to
require.contextuses a lookbehind expression like/(?<!.spec).(js|tsx)$/, swc transforms it toRegExp("(?<!.spec).(js|tsx)$"). Playgroundwebpack only processes
require.contextif the provided regex is a literal and otherwise skips it. So in our case, removing the lookbehind made swc keep it as a literal and it worked for us. Another option is to set the target toES2022(if the project allows) where swc will keep it as a literal too.Though it would be nice if
swc-loadercould be smart about this and not transformrequire.contextarguments but I'm not sure how feasible that is.