You May need additional loader to handle the result of these loaders #881

samuelsodhs · 2021-05-18T08:20:41Z

Bug report

Before opening an issue, make sure to read the contributing guide and understand this is a bug tracker, not a support platform.

Please make sure to check the following boxes before submitting an issue.
Issues opened without using this template will be closed unless they have a good reason not to follow this template.

All peer dependencies are installed: React, ReactDOM and Leaflet.
Using a supported version of React and ReactDOM (v17.0.0 minimum).
Using the supported version of Leaflet (v1.7.1 minimum) and its corresponding CSS file is loaded.
Using the latest v3 version of React-Leaflet.
The issue has not already been reported.
Make sure you have followed the quick start guide for Leaflet.
Make sure you have fully read the documentation and that you understand the limitations.

Expected behavior

Please describe.

Actual behavior

Please describe.

Steps to reproduce

Please provide the simplest example possible to reproduce the issue, based on this CodePen.

samuelsodhs · 2021-05-18T08:21:12Z

./node_modules/@react-leaflet/core/esm/path.js 10:41
Module parse failed: Unexpected token (10:41)
File was processed with these loaders:

./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
| useEffect(function updatePathOptions() {
| if (props.pathOptions !== optionsRef.current) {

  const options = props.pathOptions ?? {};

| element.instance.setStyle(options);
| optionsRef.current = options;

Sata51 · 2021-05-18T09:06:05Z

In my case, this has removed the issue facebook/create-react-app#9468 (comment)

anthify · 2021-05-18T10:29:56Z

If you're using Next.js the only way I've been able to get it to work is by using next-transpile-modules

// next.config.js

const withTM = require("next-transpile-modules")([
  "react-leaflet",
  "@react-leaflet/core",
]);

module.exports = withTM({
  future: {
    webpack5: true
  }
});

niklasnatter · 2021-05-18T14:39:03Z

You might be able to fix this by using the @babel/plugin-proposal-nullish-coalescing-operator in your project. See #883 for why this is happening.

chaincodedev · 2021-05-18T15:38:09Z

Hello Guys,

Getting same error while building my next js project and none of the solution is working for me mentioned here.

https://exerror.com/failed-to-compile-node_modules-react-leaflet-core-esm-path-js-1041-module-parse-failed-unexpected-token-1041/

Please help me or shall we remove this module and use any other since we got a BUG here now.

PLEASE HELP!!!!!!!

chaincodedev · 2021-05-18T15:39:19Z

anthify · 2021-05-19T07:32:28Z

@gurpreerrajpal have you tried my recommendation? It worked perfectly fine for me after doing this.

If you're using Next.js the only way I've been able to get it to work is by using next-transpile-modules

// next.config.js

const withTM = require("next-transpile-modules")([
  "react-leaflet",
  "@react-leaflet/core",
]);

module.exports = withTM({
  future: {
    webpack5: true
  }
});

chaincodedev · 2021-05-19T08:55:12Z

@anthify How can i write this ? I have to use withCSS as well. Appriciate your help!

"@react-leaflet/core",

]);

module.exports = withTM({
future: {
webpack5: true
}
});

module.exports = withCSS({
cssLoaderOptions: {
url: false
},
onDemandEntries: {
// period (in ms) where the server will keep pages in the buffer
maxInactiveAge: 1000 * 60 * 60 * 24 * 30, // 1 month
// number of pages that should be kept simultaneously without being disposed
pagesBufferLength: 100,
},
env: dotenv.config().parsed,
});

chaincodedev · 2021-05-22T15:08:14Z

hello guys?????? anyone able to fix it???

yodivanbaped · 2021-05-28T12:22:56Z

any other options to solve this problem? I've tried all the solutions posted here and still same issue

anthify · 2021-06-01T14:27:53Z

@chaincodedev this should work with your setup. I presume you're using an older version of next.js as you don't need withCSS anymore, but here is how you'd compose those plugins.

const withPlugins = require("next-compose-plugins");
const withCSS = require("..."); // <-- Add in your withCSS package
const withTM = require("next-transpile-modules")([
  "react-leaflet",
  "@react-leaflet/core",
]);

module.exports = withPlugins([
  [
    withTM,
    {
      future: {
        webpack5: true,
      },
    },
  ],
  [
    withCSS,
    {
      cssLoaderOptions: {
        url: false,
      },
      onDemandEntries: {
        // period (in ms) where the server will keep pages in the buffer
        maxInactiveAge: 1000 * 60 * 60 * 24 * 30, // 1 month
        // number of pages that should be kept simultaneously without being disposed
        pagesBufferLength: 100,
      },
      env: dotenv.config().parsed,
    },
  ],
]);

cLupus · 2021-06-02T09:26:07Z

I'm having the same issue, when using [email protected] / create-creat-app, which uses Webpack 4. @nnatter's suggestion / reference (to change "browserslist") seem to work in this case.

jlahd · 2021-06-09T08:37:00Z

Here's my workaround for this one (create-react-app, latest react-leaflet). Hopefully useful for someone stumbling on the issue as well. The browser list changes suggested above did not work for me (yarn start just forced a refresh of the configuration).

I ended up using the two libraries react-app-rewired and react-app-rewire-babel-loader. Steps necessary:

yarn add -D react-app-rewired react-app-rewire-babel-loader
Change script names in package.json according to the instructions for react-app-rewired:

  /* package.json */

  "scripts": {
-   "start": "react-scripts start",
+   "start": "react-app-rewired start",
-   "build": "react-scripts build",
+   "build": "react-app-rewired build",
-   "test": "react-scripts test",
+   "test": "react-app-rewired test",
    "eject": "react-scripts eject"
}

Create config-overrides.js in the project's root according to instructions for react-app-rewire-babel-loader:

/* config-overrides.js */

const path = require("path");
const fs = require("fs");
const rewireBabelLoader = require("react-app-rewire-babel-loader");
 
const appDirectory = fs.realpathSync(process.cwd());
const resolveApp = relativePath => path.resolve(appDirectory, relativePath);

module.exports = function override(config, env) {
    config = rewireBabelLoader.include(
        config,
        resolveApp("node_modules/@react-leaflet")
    );
    config = rewireBabelLoader.include(
        config,
        resolveApp("node_modules/react-leaflet")
    );

    return config;
};

And then it works. Basically, this includes react-leaflet in babel transpilation, correctly processing the ?? operators.

uafrontender · 2021-06-10T06:00:07Z

If you're using Next.js the only way I've been able to get it to work is by using next-transpile-modules

// next.config.js

const withTM = require("next-transpile-modules")([
  "react-leaflet",
  "@react-leaflet/core",
]);

module.exports = withTM({
  future: {
    webpack5: true
  }
});

This one works great for me. Now I get just warning when running yarn dev
Watchpack Error (initial scan): Error: ENOTDIR: not a directory, scandir 'node_modules/next/dist/next-server/lib/router/utils/resolve-rewrites.js'

vanshitamanral · 2021-06-10T06:25:47Z

restricting the react-leaflet to the older versions might help some of you, as it helped me :)


     "react-leaflet": ">=3.1.0 <3.2.0 || ^3.2.1",
    "@react-leaflet/core": ">=1.0.0 <1.1.0 || ^1.1.1",

also updating the browsers list to
"browserslist":[
">0.2%",
"not dead",
"not op_mini all"
]
and then remove the node modules folder.
type in npm install in the terminal
and then npm start and this might solve your issue :)

josegoval · 2021-07-14T10:27:31Z

If you're using Next.js the only way I've been able to get it to work is by using next-transpile-modules

// next.config.js

const withTM = require("next-transpile-modules")([
  "react-leaflet",
  "@react-leaflet/core",
]);

module.exports = withTM({
  future: {
    webpack5: true
  }
});

Use version 7.2.0.

"next-transpile-modules": "^7.2.0",

Version 8.0.0 give the next error:

(node:16082) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'startsWith' of undefined
    at handleExternals (projectPath/node_modules/next/dist/build/webpack-config.js:36:23)
    at webpackConfig.externals (projectPath/node_modules/next/dist/build/webpack-config.js:78:149)
    at projectPath/node_modules/next-transpile-modules/src/next-transpile-modules.js:238:46
    at handleExternals (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61039:17)
    at next (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61027:9)
    at handleExternals (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61032:7)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61062:5
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:67817:5
    at AsyncSeriesWaterfallHook.eval [as callAsync] (eval at create (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:47182:10), <anonymous>:6:1)
    at AsyncSeriesWaterfallHook.lazyCompileHook (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:47119:20)
    at NormalModuleFactory.create (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:67798:28)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54821:14
    at Semaphore.acquire (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:93226:4)
    at asyncLib.forEach.err.stack (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54819:15)
    at arrayEach (projectPath/node_modules/next/dist/compiled/neo-async/async.js:1:5951)
    at Object.each (projectPath/node_modules/next/dist/compiled/neo-async/async.js:1:9550)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:16082) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
(node:16082) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:16082) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'startsWith' of undefined
    at handleExternals (projectPath/node_modules/next/dist/build/webpack-config.js:36:23)
    at webpackConfig.externals (projectPath/node_modules/next/dist/build/webpack-config.js:78:149)
    at projectPath/node_modules/next-transpile-modules/src/next-transpile-modules.js:238:46
    at handleExternals (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61039:17)
    at next (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61027:9)
    at handleExternals (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61032:7)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61062:5
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:67817:5
    at AsyncSeriesWaterfallHook.eval [as callAsync] (eval at create (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:47182:10), <anonymous>:6:1)
    at NormalModuleFactory.create (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:67798:28)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54821:14
    at Semaphore.acquire (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:93226:4)
    at asyncLib.forEach.err.stack (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54819:15)
    at arrayEach (projectPath/node_modules/next/dist/compiled/neo-async/async.js:1:5951)
    at Object.each (projectPath/node_modules/next/dist/compiled/neo-async/async.js:1:9550)
    at Compilation.addModuleDependencies (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54797:12)
(node:16082) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 7)
(node:16082) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'startsWith' of undefined
    at handleExternals (projectPath/node_modules/next/dist/build/webpack-config.js:36:23)
    at webpackConfig.externals (projectPath/node_modules/next/dist/build/webpack-config.js:78:149)
    at projectPath/node_modules/next-transpile-modules/src/next-transpile-modules.js:238:46
    at handleExternals (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61039:17)
    at next (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61027:9)
    at handleExternals (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61032:7)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61062:5
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:67817:5
    at AsyncSeriesWaterfallHook.eval [as callAsync] (eval at create (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:47182:10), <anonymous>:6:1)
    at NormalModuleFactory.create (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:67798:28)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54821:14
    at Semaphore.acquire (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:93226:4)
    at asyncLib.forEach.err.stack (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54819:15)
    at arrayEach (projectPath/node_modules/next/dist/compiled/neo-async/async.js:1:5951)
    at Object.each (projectPath/node_modules/next/dist/compiled/neo-async/async.js:1:9550)
    at Compilation.addModuleDependencies (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54797:12)
(node:16082) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8)
(node:16082) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'startsWith' of undefined
    at handleExternals (projectPath/node_modules/next/dist/build/webpack-config.js:36:23)
    at webpackConfig.externals (projectPath/node_modules/next/dist/build/webpack-config.js:78:149)
    at projectPath/node_modules/next-transpile-modules/src/next-transpile-modules.js:238:46
    at handleExternals (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61039:17)
    at next (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61027:9)
    at handleExternals (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61032:7)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61062:5
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:67817:5
    at AsyncSeriesWaterfallHook.eval [as callAsync] (eval at create (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:47182:10), <anonymous>:6:1)
    at NormalModuleFactory.create (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:67798:28)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54987:18
    at Semaphore.acquire (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:93226:4)
    at Compilation._addModuleChain (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54986:18)
    at Compilation.addEntry (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:55088:8)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:59990:19
    at new Promise (<anonymous>)
(node:16082) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)
(node:16082) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'startsWith' of undefined
    at handleExternals (projectPath/node_modules/next/dist/build/webpack-config.js:36:23)
    at webpackConfig.externals (projectPath/node_modules/next/dist/build/webpack-config.js:78:149)
    at projectPath/node_modules/next-transpile-modules/src/next-transpile-modules.js:238:46
    at handleExternals (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61039:17)
    at next (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61027:9)
    at handleExternals (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61032:7)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:61062:5
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:67817:5
    at AsyncSeriesWaterfallHook.eval [as callAsync] (eval at create (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:47182:10), <anonymous>:6:1)
    at NormalModuleFactory.create (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:67798:28)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54987:18
    at Semaphore.acquire (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:93226:4)
    at Compilation._addModuleChain (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:54986:18)
    at Compilation.addEntry (projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:55088:8)
    at projectPath/node_modules/next/dist/compiled/webpack/bundle4.js:59990:19
    at new Promise (<anonymous>)
(node:16082) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 10)

tilnea · 2021-07-14T11:01:07Z

For me, it breaks with storybook

    "@storybook/addon-essentials": "^6.3.3",
    "@storybook/addon-links": "^6.3.3",
    "@storybook/node-logger": "^6.3.3",
    "@storybook/preset-create-react-app": "^3.2.0",
    "@storybook/react": "^6.3.3",

and I'm using "react-leaflet": "^3.2.0"
in a create-react-app

DigitalNaut · 2021-07-16T01:50:32Z

(Adding this since it was the first Google search results for me and I had to dig around for a couple of hours.)

For CRACO using react-leaflet 3.2.0, there's a simple solution that worked for me that uses the @babel/babel-plugin-proposal-nullish-coalescing-operator.

Run:
npm install --save-dev @babel/plugin-proposal-nullish-coalescing-operator

And add this to craco.config.js:

module.exports = {
  babel: {
    plugins: ["@babel/plugin-proposal-nullish-coalescing-operator"],
  },
};

anthify · 2021-07-20T11:49:49Z

Hey @josegoval

I'm using the following package versions:

"next-transpile-modules": "7.1.1"
"next": "10.1.3"
"react-leaflet": "3.2.0"
"leaflet": "1.7.1"

with Node.js version 12.13.1

Hopefully that helps

KhadijaMahanga · 2021-07-21T21:23:26Z

For me, it breaks with storybook

    "@storybook/addon-essentials": "^6.3.3",
    "@storybook/addon-links": "^6.3.3",
    "@storybook/node-logger": "^6.3.3",
    "@storybook/preset-create-react-app": "^3.2.0",
    "@storybook/react": "^6.3.3",

and I'm using "react-leaflet": "^3.2.0"
in a create-react-app

@tilnea did you find a solution? I am having the same issue. Breaks on storybook

Niolak · 2021-07-22T07:39:46Z

@KhadijaMahanga To fix storybook (using create-react-app and react-leaflet 3.2.0), adding @babel/plugin-proposal-nullish-coalescing-operator in dev-dependencies and creating this file works for me:

babel.config.js

module.exports = {
  presets: [
    [
      '@babel/preset-env',
      {
        targets: {
          ie: '11',
        },
      },
    ],
    '@babel/preset-react',
  ],
  plugins: ["@babel/plugin-proposal-nullish-coalescing-operator"],
};

KhadijaMahanga · 2021-07-22T10:00:56Z

@tilnea for storybook, this is what I added.

 webpackFinal: async (config) => {
    config.module.rules.push({
      test: /\.(js|jsx)$/,
      loader: require.resolve("babel-loader"),
      options: {
        plugins: [
          "@babel/plugin-proposal-nullish-coalescing-operator",
        ],
      },
    });

    return config;
  },

collisio · 2021-08-06T18:50:32Z

We were able to get our Storybook to build on Vercel using the following configuration:

package.json:

"@react-leaflet/core": "1.0.2",
"leaflet": "^1.7.1",
"react-leaflet": "3.1.0",
"storybook": "^6.3.6",
"next": "^11.0.0",

.storybook/main.js

// other stuff
  webpackFinal: async (config, { configType }) => {
    // more configuration options
    config.module.rules.push({
      test: /\.(js|jsx)$/,
      loader: require.resolve("babel-loader"),
      options: {
        presets: [
          '@babel/preset-env',
          '@babel/preset-react',
        ],
        plugins: [
          "@babel/plugin-proposal-nullish-coalescing-operator",
        ],
      },
    });
    return config;
  },
// other stuff

nitish166 · 2021-09-19T04:23:13Z

restricting the react-leaflet to the older versions might help some of you, as it helped me :)
     "react-leaflet": ">=3.1.0 <3.2.0 || ^3.2.1",
    "@react-leaflet/core": ">=1.0.0 <1.1.0 || ^1.1.1",
also updating the browsers list to
"browserslist":[
">0.2%",
"not dead",
"not op_mini all"
]
and then remove the node modules folder.
type in npm install in the terminal
and then npm start and this might solve your issue :)

Thanks Man!

SohanR · 2021-09-25T17:53:56Z

This helps me to fix exact same problem facebook/create-react-app#9468 (comment)

but after change "Browserlist" do the followings

Delete your node_modules folder
Run npm cache clean --force
Run npm install

Now everything should work as expected. If the map is not loaded, don't forget to add the leaflet css and js to your page and set the height for your MapContainer. See the official documentation for more information.

PaulLeCam · 2021-10-09T15:59:25Z

Duplicate of already closed issue.

morganney · 2021-10-10T13:33:26Z

@PaulLeCam why do you not want to transpile the nullish coalescing operator before publishing this package?

Zerg00s · 2021-10-18T01:21:36Z

Same issue. Tried a clean create-react-app with typescript. Then followed the official react-leaflet tutorial.

Note the bug & workaround: PaulLeCam/react-leaflet#881 (comment)

crescit · 2021-10-30T05:03:02Z

Just went down this rabbit hole, and this was the thing that resolved it for me after trying all of the above. Used nvm to go down to node 14 as well. facebook/create-react-app#9468 (comment)

jbalums · 2022-10-24T17:03:00Z

In my case, this has removed the issue facebook/create-react-app#9468 (comment)

thank you this solves my problem

davidko5 · 2024-04-25T12:42:24Z

Still have this issue. node v12.22.12, yarn 1.22.4, tried editing package.json browsersList + deleting node_modules/.cache as well as adding "plugin-transform-nullish-coalescing-operator" babel plugin.

DigitalNaut · 2024-04-25T14:50:26Z

Still have this issue. node v12.22.12, yarn 1.22.4, tried editing package.json browsersList + deleting node_modules/.cache as well as adding "plugin-transform-nullish-coalescing-operator" babel plugin.

Whoa, you have a very old version of Node. The latest version is v20. Can you update to a recommended version? (Also, I recommend porting your projects to PNPM instead of Yarn. It's way faster and centralizes your dependencies to save a ton of disk space.)

niklasnatter mentioned this issue May 18, 2021

Nullish coalescing operator makes package incompatible with webpack 4 #883

Closed

ilindaniel mentioned this issue Jun 13, 2021

Can't compile react-leaflet #891

Closed

PaulLeCam closed this as completed Oct 9, 2021

tnottu added a commit to tnottu/parking-exercise that referenced this issue Oct 24, 2021

Add OpenStreetMap. Improve app styles.

858482b

Note the bug & workaround: PaulLeCam/react-leaflet#881 (comment)

weswithley mentioned this issue Jul 1, 2022

Module parse failed: Unexpected token (10:41) in @react-leaflet/core/esm/path.js #877

Closed

7 tasks

mhzendehpey mentioned this issue Jul 31, 2022

You may need an additional loader to handle the result of these loaders. #1010

Closed

You May need additional loader to handle the result of these loaders #881

You May need additional loader to handle the result of these loaders #881

Comments

samuelsodhs commented May 18, 2021

Bug report

Expected behavior

Actual behavior

Steps to reproduce

samuelsodhs commented May 18, 2021

Uh oh!

Sata51 commented May 18, 2021

Uh oh!

anthify commented May 18, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

niklasnatter commented May 18, 2021

Uh oh!

chaincodedev commented May 18, 2021

Uh oh!

chaincodedev commented May 18, 2021

Uh oh!

anthify commented May 19, 2021

Uh oh!

chaincodedev commented May 19, 2021

Uh oh!

chaincodedev commented May 22, 2021

Uh oh!

yodivanbaped commented May 28, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anthify commented Jun 1, 2021

Uh oh!

cLupus commented Jun 2, 2021

Uh oh!

jlahd commented Jun 9, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

uafrontender commented Jun 10, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vanshitamanral commented Jun 10, 2021

Uh oh!

josegoval commented Jul 14, 2021

Uh oh!

tilnea commented Jul 14, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

DigitalNaut commented Jul 16, 2021

Uh oh!

anthify commented Jul 20, 2021

Uh oh!

KhadijaMahanga commented Jul 21, 2021

Uh oh!

Niolak commented Jul 22, 2021

Uh oh!

KhadijaMahanga commented Jul 22, 2021

Uh oh!

collisio commented Aug 6, 2021

Uh oh!

nitish166 commented Sep 19, 2021

Uh oh!

SohanR commented Sep 25, 2021

Uh oh!

PaulLeCam commented Oct 9, 2021

Uh oh!

morganney commented Oct 10, 2021

Uh oh!

Zerg00s commented Oct 18, 2021

Uh oh!

crescit commented Oct 30, 2021

Uh oh!

jbalums commented Oct 24, 2022

Uh oh!

davidko5 commented Apr 25, 2024

Uh oh!

DigitalNaut commented Apr 25, 2024

Uh oh!

anthify commented May 18, 2021 •

edited

Loading

yodivanbaped commented May 28, 2021 •

edited

Loading

jlahd commented Jun 9, 2021 •

edited

Loading

uafrontender commented Jun 10, 2021 •

edited

Loading

tilnea commented Jul 14, 2021 •

edited

Loading