Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

[creage]

Trying to build a TypeScript project using Webpack5 throws an error:

Compiled with problems:

WARNING in ./node_modules/universal-geocoder/dist/esm/utils.js 74:10-17

Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

Switching to CJS does not help - it fires same error for the cjs/utils.js

import UniversalGeocoder from 'universal-geocoder';

const geocoder = UniversalGeocoder.createGeocoder({
    provider: 'googlemaps',
    apiKey: 'KEY',
    useSsl: true,
    useJsonp: false
});

geocoder.geocode({
    text: '1600 Pennsylvania Ave, Washington, DC',
    locale: 'FR',
    limit: 10
}).then(console.log);

[alanpoulain]

It's because this project needs the crypto module only in Node.js:

universal-geocoder-js/src/provider/googlemaps/GoogleMapsProvider.ts

Line 686 in 4fbeed9

const crypto = getRequireFunc()("crypto");

Since this library is isomorphic, I needed to use this special function to make it work everywhere:

universal-geocoder-js/src/utils.ts

Lines 90 to 95 in 4fbeed9

	export const getRequireFunc = (): Function =>
	// eslint-disable-next-line camelcase
	typeof __non_webpack_require__ === "function"
	? // eslint-disable-next-line camelcase
	__non_webpack_require__
	: require;

That's why TypeScript is telling you that it cannot extract the dependencies statically. It's only a warning though, not an error.
If you find a better way to do it, please tell me.

[creage]

How about separating browser and node parts? And letting people import just the part they need?

The way it is implemented right now doesn't seem to be universal much. I mean, I can compile, but my CI/CD pipeline won't allow that code.