fix: webpack import meta error (#114)

I did some investigation about this and it turns out our transpiled JS
code is the following (published package)
here import.meta is accessed directly, however
https://webpack.js.org/api/module-variables/ states that you cannot
directly access import.meta instead, access its properties or
de-structure it
I believe this affects all projects using webpack and we might need to
update the code for this function


![image](https://github.com/user-attachments/assets/8194609a-d417-48be-84f1-461a0b146fdf)

![image](https://github.com/user-attachments/assets/ea87730a-24c1-40d3-a95a-88b574f9b4e5)

---------

Co-authored-by: BeroBurny <[email protected]>

Author: saadahmsiddiqui

packages/sdk/src/node.d.ts

@@ -0,0 +1,3 @@
+interface ImportMeta {
+  env: string;
+}

packages/sdk/src/utils.ts

@@ -3,7 +3,7 @@ export function getEnv(envName: string, defaultValue: string): string {
   try {
     if (typeof process !== "undefined" && "env" in process)
       variable = process.env[envName];
-    else if ("env" in import.meta) {
+    else if (import.meta.env) {
       const env =
         // @ts-expect-error @typescript-eslint/ban-ts-comment
         (import.meta.env as { [key: string]: string | undefined }) || {};