Getting Error after updating to 0.1.11. (0.1.9 was working fine).

[mr-tm]

Seems to be error for Expo/NextJS projects which have packages that depends on this library.

Basically, compiler started to fail after 0.1.10-0.1.11 update. (0.1.9 was working fine)

Module parse failed: Cannot use 'import.meta' outside a module (99:16)
|                 // still a Refresh Boundary later.
|                 // @ts-ignore importMeta is replaced in the loader
>                 import.meta.webpackHot.accept();
|                 // This field is set when the previous version of this module was a
|                 // Refresh Boundary, letting us know we need to check for invalidation or

Import trace for requested module:
../../node_modules/react-native-paper/node_modules/use-latest-callback/lib/src/index.js
../../node_modules/react-native-paper/node_modules/use-latest-callback/esm.mjs
../../node_modules/react-native-paper/lib/module/components/Banner.js
../../node_modules/react-native-paper/lib/module/index.js
 GET / 500 in 111ms
 ⨯ ../../node_modules/react-native-paper/node_modules/use-latest-callback/lib/src/index.js
Module parse failed: Cannot use 'import.meta' outside a module (99:16)
|                 // still a Refresh Boundary later.
|                 // @ts-ignore importMeta is replaced in the loader
>                 import.meta.webpackHot.accept();
|                 // This field is set when the previous version of this module was a
|                 // Refresh Boundary, letting us know we need to check for invalidation or

Import trace for requested module:
../../node_modules/react-native-paper/node_modules/use-latest-callback/lib/src/index.js
../../node_modules/react-native-paper/node_modules/use-latest-callback/esm.mjs
../../node_modules/react-native-paper/lib/module/components/Banner.js
../../node_modules/react-native-paper/lib/module/index.js

[mr-tm]

Putting this override in package.json, fixes the issue.

"overrides": {
    "react-native-paper": {
      "use-latest-callback": "0.1.9"
    }
  },

[satya164]

Please share a repro. Though this looks like a bug in Next.js

Related: vercel/next.js#35110