Vasily Belosloodcev bupy7

Map Tiles

Google Maps

http://{s}.google.com/vt/lyrs=m&x={x}&y={y}&z={z} - Subdomains: mt0, mt1, mt2, mt3. - Examples: - https://mts1.google.com/vt/x=1325&y=3143&z=13 - https://mt1.google.com/vt/lyrs=m&x=1325&y=3143&z=13 - Additional info:

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

Use ESM yourself. (preferred)
Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.

Using TypeScript Node.js with native ESM

This reference guide shows how to configure a TypeScript Node.js project to work and compile to to native ESM.

Rationale

CommonJS module system was introduced by the Node.js developers due to the lack of the notion of "modules" in the original JavaScript (ECMAScript) language specification at that time. However, nowadays, ECMAScript has a standard module system called ESM — ECMAScript Modules, which is a part of the accepted standard. This way CommonJS could be considered vendor-specific and obsolete/legacy. Hopefully, TypeScript ecosystem now supports the "new" standard.

So the key benefits are:

	function useSelectors(reducer, mapStateToSelectors) {
	const [state] = reducer;
	const selectors = useMemo(() => mapStateToSelectors(state), [state]);
	return selectors;
	}

	function useActions(reducer, mapDispatchToActions) {
	const [, dispatch] = reducer;
	const actions = useMemo(() => mapDispatchToActions(dispatch), [dispatch]);
	return actions;