import.meta.env is not supported

[tux21b]

I am not really familiar with this import.meta stuff, but importing jotai leads to the following warnings:

▲ [WARNING] "import.meta" is not available in the configured target environment ("chrome58", "edge18", "firefox57", "safari11") and will be empty

    ../node_modules/jotai/esm/index.mjs:66:7:
      66 │   if ((import.meta.env && import.meta.env.MODE) !== "production") {
         ╵        ~~~~~~~~~~~

▲ [WARNING] "import.meta" is not available in the configured target environment ("chrome58", "edge18", "firefox57", "safari11") and will be empty

    ../node_modules/jotai/esm/index.mjs:66:26:
      66 │   if ((import.meta.env && import.meta.env.MODE) !== "production") {
         ╵                           ~~~~~~~~~~~

The code only checks the existence of import.meta.env so i guess import.meta should always exist. It seems to work with other bundlers (webpack).

[hyrious]

import.meta.env is not in the scope of esbuild, you will have to add your own --define:import.meta.env={}. The jotai package makes the assumption that their users are using webpack. But other bundlers (including rollup) do not agree with that.

If there exists one common env variable, it has to be process.env.NODE_ENV. But someone also wants to remove that. So I guess there's no perfect solution.

[tux21b]

Thanks for your quick reply. I was able to solve my problem in the meantime.

Apparently import.meta.env is supported by esbuild, but it needs ES2020 as mentioned here:
#1492

I was able to fix it by updating the supported engines slightly:

api.EngineChrome: 58 -> 64
api.EngineFirefox: 57 -> 62
api.EngineSafari: 11 -> 11.1
api.EngineEdge: 18 -> 79

Now everything seems to work as expected. Thanks :)