Hermes Alves Comments - Answer Overflow

•Created by Hermes Alves on 11/14/2024 in #❓・help

Nuxt 4 - compability version (node:81791) Warning: To load an ES module, set "type": "module" in...

@kapa.ai I'm encountering a persistent warning while running my Nuxt 3.14.159 application using both Bun and npm as package managers. The warning appears as follows: (node:84434) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.

Nuxt Version: 3.14.159
Nitro Version: 2.10.4
Compatibility Version: 4 (set via compatibilityDate: '2024-04-03' and future: { compatibilityVersion: 4 })
Package Managers Tested: Bun and npm
Node.js Version: v22.2.0

Nuxt Version: 3.14.159
Nitro Version: 2.10.4
Compatibility Version: 4 (set via compatibilityDate: '2024-04-03' and future: { compatibilityVersion: 4 })
Package Managers Tested: Bun and npm
Node.js Version: v22.2.0

The warning appears during both development (npm run dev and bun run dev) and build processes. The application runs, but I’m concerned that this warning may indicate an underlying issue that could affect future updates or production stability. 1. Is this warning indicative of a deeper problem that should be addressed? 2. Are there specific configurations or steps I might be overlooking to resolve this? 3. Could the compatibility version setting be related, and if so, is there a way to address it without the warning?

8 replies

•Created by Hermes Alves on 11/14/2024 in #❓・help

Nuxt 4 - compability version (node:81791) Warning: To load an ES module, set "type": "module" in...

@kapa.ai I'm encountering a persistent warning while running my Nuxt 3.14.159 application using both Bun and npm as package managers. The warning appears as follows: (node:84434) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.

Nuxt Version: 3.14.159
Nitro Version: 2.10.4
Compatibility Version: 4 (set via compatibilityDate: '2024-04-03' and future: { compatibilityVersion: 4 })
Package Managers Tested: Bun and npm
Node.js Version: v22.2.0

Nuxt Version: 3.14.159
Nitro Version: 2.10.4
Compatibility Version: 4 (set via compatibilityDate: '2024-04-03' and future: { compatibilityVersion: 4 })
Package Managers Tested: Bun and npm
Node.js Version: v22.2.0

The warning appears during both development (npm run dev and bun run dev) and build processes. The application runs, but I’m concerned that this warning may indicate an underlying issue that could affect future updates or production stability. 1. Is this warning indicative of a deeper problem that should be addressed? 2. Are there specific configurations or steps I might be overlooking to resolve this? 3. Could the compatibility version setting be related, and if so, is there a way to address it without the warning?

8 replies

•Created by Hermes Alves on 10/26/2024 in #❓・help

How to Add Dynamic Pages/Extensions in Nuxt 4 at Runtime? Need Ideas for My Bun-based Open project

I appreciate the response, but I’m specifically looking for insights from people who have faced similar challenges or have experience with this kind of implementation. Personal experiences would be really helpful in guiding my approach.

7 replies

•Created by Hermes Alves on 10/15/2024 in #help

Why isn't the API_PORT variable being loaded? Is there something I'm missing?

Thanks for your attentions guys

15 replies

•Created by Hermes Alves on 10/15/2024 in #help

Why isn't the API_PORT variable being loaded? Is there something I'm missing?

I'm new to Deno and I have a question regarding environment variables. For development, I need to specify the path to my .env file using dotenv to load the environment variables. However, when running in production (inside a Docker container), I assume I don't need to use dotenv since Docker can handle environment variables directly. Is my understanding correct? Do I need to manage .env files differently for development and production?

15 replies

•Created by Hermes Alves on 10/15/2024 in #help

Why isn't the API_PORT variable being loaded? Is there something I'm missing?

Yes, with a specify the envPath this work´s: const envVar = await load({envPath: "../.env", export: true})

15 replies

•Created by Hermes Alves on 10/15/2024 in #help

Why isn't the API_PORT variable being loaded? Is there something I'm missing?

15 replies

•Created by Hermes Alves on 10/15/2024 in #help

Why isn't the API_PORT variable being loaded? Is there something I'm missing?

Didn´t work too.

# API 
JWT_SECRET=$omeRand0mStr1ng
API_PORT=3737

# API 
JWT_SECRET=$omeRand0mStr1ng
API_PORT=3737

15 replies

•Created by Hermes Alves on 10/15/2024 in #help

Why isn't the API_PORT variable being loaded? Is there something I'm missing?

The .env file is located in the root of the project, alongside the deno.json. The api folder contains the Hono-based API project. Here's the structure:

/.env
/deno.json
/api
  ├── app.ts
  ├── controllers
  ├── models
  ├── routes
  ├── services

/.env
/deno.json
/api
  ├── app.ts
  ├── controllers
  ├── models
  ├── routes
  ├── services

Any idea why the API_PORT isn't loading?

15 replies

•Created by Hermes Alves on 11/20/2023 in #❓・help

localhost:3000/api/analytics import it's not accepted? @google-analytics/data

Yes, with the new version it's working

4 replies

•Created by Hermes Alves on 11/27/2023 in #general-help

typescript sdk for KV?

?

11 replies

•Created by Hermes Alves on 11/27/2023 in #general-help

typescript sdk for KV?

wrangler dev [<SCRIPT>] [OPTIONS]

11 replies

•Created by Hermes Alves on 11/27/2023 in #general-help

typescript sdk for KV?

For local test, I will need to use

11 replies

•Created by Hermes Alves on 11/27/2023 in #general-help

typescript sdk for KV?

My project uses cloudflare pages, made with Nuxt 3 .

11 replies

•Created by Hermes Alves on 11/27/2023 in #general-help

typescript sdk for KV?

It's not just about typescript, I'm new with kV. With redis we have a sdk to connect and put and get the key values from database. How can I do that with kV? Just command line for terminal or request API rest by endpoint?

11 replies