Configuration seems to struggle with Next.js PWA configurations

[haykam821]

I am working on migrating a web application to Next.js in this repo. However, I am running into an issue where the basePath is seemingly not injected.

My configuration looks like the following:

const withPWA = require("next-pwa")({
	dest: "public",
});

module.exports = withPWA({
	compiler: {
		styledComponents: true,
	},
	reactStrictMode: true,
});

However, the step using the actions/configure-pages action outputs this warning from #43:

Warning: Unsupported configuration file extension. Currently supported extensions: ".js", ".cjs", ".mjs"

Other than the fact that the next.config.js configuration uses the .js extension, it seems that the action fails to inject properties into a configuration wrapped by a higher-order withPWA function. A more useful error is not logged, so this issue is hard to diagnose.

[zvailanu98]

I'm having the same issue with withContentlayer(). A lot of Next.js "plugins" wrap the config in this way, which doesn't seem to work with this action.

[DenizUgur]

Weird that no workaround or fix has been proposed here

[haykam821]

This action seems to support wrapping calls already, but the functionality for doing so seems to not be enabled. The ConfigParser constructor simply needs to be passed allowWrappingCall: true in its settings:

configure-pages/src/set-pages-config.js

Lines 77 to 79 in f156874

	// Parse the configuration file and try to inject the Pages configuration in it
	const settings = getConfigParserSettings({ staticSiteGenerator, generatorConfigFile, siteUrl })
	new ConfigParser(settings).injectAll()

The parsing for wrapping calls only seems to allow one wrapping call, though, so multiple higher-order functions would not be usable even if allowWrappingCall: true was specified.

[atkinchris]

I've raised a PR to introduce @haykam821's fix here: #161.