[BUG][@opentelemetry] Could not resolve "../platform" #219

NayamAmarshe · 2025-01-01T00:27:33Z

Describe the bug

I'm using firebase + Next.js 14 API Route Handlers. I've added force-dynamic to all the required routes and pages but when I do npm run preview:worker it throws the following error:

> dev:worker
> wrangler dev --port 8771


 ⛅️ wrangler 3.99.0
-------------------

Using vars defined in .dev.vars
Your worker has access to the following bindings:
- Vars:
  - NEXTJS_ENV: "(hidden)"
  - NODE_ENV: "(hidden)"
[wrangler:inf] Ready on http://localhost:8771
▲ [WARNING] Suspicious assignment to defined constant "process.env.NODE_ENV" [assign-to-define]

    .open-next/server-functions/default/handler.mjs:32217:4:
      32217 │     process.env.NODE_ENV = "production";
            ╵     ~~~~~~~~~~~~~~~~~~~~

  The expression "process.env.NODE_ENV" has been configured to be replaced with a constant using the "define" feature. If this expression is supposed to be a compile-time constant, then it doesn't make sense to assign to it here. Or if this expression is supposed to change at run-time, this "define" substitution should be removed.



✘ [ERROR] Build failed with 1 error:

  ✘ [ERROR] Could not resolve "../platform"
  
  
  .open-next/server-functions/default/node_modules/@opentelemetry/api/build/src/internal/global-utils.js:19:27:
        19 │ const platform_1 = require("../platform");
           ╵                            ~~~~~~~~~~~~~
  
  


▲ [WARNING] Suspicious assignment to defined constant "process.env.NODE_ENV" [assign-to-define]

    .open-next/server-functions/default/handler.mjs:32217:4:
      32217 │     process.env.NODE_ENV = "production";
            ╵     ~~~~~~~~~~~~~~~~~~~~

  The expression "process.env.NODE_ENV" has been configured to be replaced with a constant using the "define" feature. If this expression is supposed to be a compile-time constant, then it doesn't make sense to assign to it here. Or if this expression is supposed to change at run-time, this "define" substitution should be removed.


🪵  Logs were written to "/Users/macbook-air/Library/Preferences/.wrangler/logs/wrangler-2025-01-01_00-21-52_196.log"

Steps to reproduce

Next.js 14 project with API route handlers and a dynamic page.
Use firebase db/auth on both static and dynamic routes.
Try running npm run preview:worker

Expected behavior

It should start the dev server

@opennextjs/cloudflare version

0.3.3

Wrangler version

3.99.0

next info output

$ npx next info         

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Dec  6 18:40:14 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T8103
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 1.22.21
  pnpm: 8.14.3
Relevant Packages:
  next: 14.2.21 // An outdated version detected (latest is 15.1.3), upgrade is highly recommended!
  eslint-config-next: 14.2.21
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.7.2
Next.js Config:
  output: N/A
 ⚠ An outdated version detected (latest is 15.1.3), upgrade is highly recommended!
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue

Additional context

No response

The text was updated successfully, but these errors were encountered:

dario-piotrowicz · 2025-01-02T22:02:39Z

Thanks a bunch for the issue @NayamAmarshe, I also noticed this issue but I wasn't sure if it was specific to the app I was working on, good to know that it's a general issue

It would really be great to have a minimal repro for this 😓

anyways I'll look into this 🙂

shahadpichen · 2025-01-08T06:05:31Z

Hi, I'm currently facing the same issue with the error:

 ✘ [ERROR] Could not resolve "../platform"
  
  
  .open-next/server-functions/default/node_modules/@opentelemetry/api/build/src/internal/global-utils.js:19:27:
        19 │ const platform_1 = require("../platform");

Any updates or workarounds would be greatly appreciated. Thanks in advance!

vicb · 2025-01-08T06:58:06Z

What help us help you it's if you can submit a repository containing a minimal repro for the issue.
Thanks

shahadpichen · 2025-01-09T06:26:30Z

Thanks for the response @vicb ! I've created a minimal repository for the issue.

You can find it here: https://github.com/shahadpichen/opentelemetry-issue.

Please let me know if you need any further details.

RickyRAV · 2025-01-14T01:04:07Z

hi there, ive come across the same issue, and we have similar tech stacks, the problem is caused by "drizzle-orm": "^0.38.3", because its using @opentelemetry/api, found it out by running: npm ls @opentelemetry/api
maybe this helps somehow

vicb · 2025-01-16T20:36:27Z

Nopsled · 2025-01-17T21:08:04Z

Also got same issue with this working with trigger.dev. Solved it like Aries with removing all dependencies in lockfile and used npm ci (instead of npm i). However I assume this means that I need to patch the lock-file each time I install a new package.

@vicb Is there any possibility to resolve this by using some older version of the adapter?

vicb · 2025-01-29T12:59:09Z

Thanks for the repro @shahadpichen.

I now understand how this happen, I only need to figure out why and then the proper fix.

A simple patch of global-utils.js fixes that:

-const platform_1 = require("../platform");
-const version_1 = require("../version");
-const semver_1 = require("./semver");
+const platform_1 = require("../platform/index.js");
+const version_1 = require("../version.js");
+const semver_1 = require("./semver.js");

vicb · 2025-01-29T13:12:07Z

A quick way to unblock ppl here is using:

WRANGLER_BUILD_CONDITIONS="" WRANGLER_BUILD_PLATFORM="node" pnpm wrangler dev
WRANGLER_BUILD_CONDITIONS="" WRANGLER_BUILD_PLATFORM="node" pnpm wrangler deploy

ref: https://opennext.js.org/cloudflare/troubleshooting#my-app-fails-to-build-when-i-import-a-specific-npm-package

We'll work on a proper fix in the coming days

vicb · 2025-01-29T14:10:04Z

You can find it here: https://github.com/shahadpichen/opentelemetry-issue.

Can I copy your repo into examples/bugs/gh-219 as a test for the fix?

i.e. does it contain any code that you do not want shared in the OpenNext repo?

vicb · 2025-01-30T11:35:15Z

Hopefully #302 should fix the issue, you can try by installing the adapter at https://pkg.pr.new/@opennextjs/cloudflare@302

Please report your experiences,

Thanks!

shahadpichen · 2025-01-30T12:09:13Z

You can find it here: https://github.com/shahadpichen/opentelemetry-issue.

Can I copy your repo into examples/bugs/gh-219 as a test for the fix?

i.e. does it contain any code that you do not want shared in the OpenNext repo?

Yah sure 👍

NayamAmarshe added bug Something isn't working triage labels Jan 1, 2025

dario-piotrowicz mentioned this issue Jan 2, 2025

Make site work with the Cloudflare OpenNext adapter nodejs/nodejs.org#7383

Merged

5 tasks

dario-piotrowicz self-assigned this Jan 2, 2025

dario-piotrowicz removed the triage label Jan 2, 2025

dario-piotrowicz moved this to Misc in opennext-cloudflare - aws "merge" Jan 2, 2025

dario-piotrowicz added this to opennext-cloudflare - aws "merge" Jan 2, 2025

dario-piotrowicz moved this from Misc to In Progress in opennext-cloudflare - aws "merge" Jan 2, 2025

This comment was marked as outdated.

Sign in to view

dario-piotrowicz mentioned this issue Jan 3, 2025

fix: patch both trace/tracer.js files #222

Closed

2 tasks

dario-piotrowicz mentioned this issue Jan 15, 2025

instead of patching the tracer.js file to throw on @opentelemetry/api imports, delete the @opentelemetry/api dependency itself #259

Closed

dario-piotrowicz moved this to Todo in `@opennextjs/cloudflare` prioritization and tracking Jan 16, 2025

dario-piotrowicz added this to `@opennextjs/cloudflare` prioritization and tracking Jan 16, 2025

dario-piotrowicz moved this from Todo to P1 - need to be addressed in `@opennextjs/cloudflare` prioritization and tracking Jan 16, 2025

dario-piotrowicz removed their assignment Jan 20, 2025

dario-piotrowicz mentioned this issue Jan 21, 2025

[BUG] Could not resolve "../platform" for @opentelemetry/api #266

Closed

vicb self-assigned this Jan 22, 2025

dario-piotrowicz mentioned this issue Jan 22, 2025

🐛 Bug: everything that's needed should be in the output directory #14

Closed

vicb mentioned this issue Jan 29, 2025

Issue with Node/Edge files - export conditions #285

Closed

vicb mentioned this issue Jan 30, 2025

fix build issues with @opentelemetry #302

Merged

vicb closed this as completed in #302 Jan 30, 2025

github-project-automation bot moved this from P1 to Done in `@opennextjs/cloudflare` prioritization and tracking Jan 30, 2025

github-project-automation bot moved this from In Progress to Done in opennext-cloudflare - aws "merge" Jan 30, 2025

vicb mentioned this issue Jan 30, 2025

add test for 219 #304

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[BUG][@opentelemetry] Could not resolve "../platform" #219

[BUG][@opentelemetry] Could not resolve "../platform" #219

NayamAmarshe commented Jan 1, 2025 •

edited

Loading

dario-piotrowicz commented Jan 2, 2025

Uh oh!

This comment was marked as outdated.

shahadpichen commented Jan 8, 2025

Uh oh!

vicb commented Jan 8, 2025

Uh oh!

shahadpichen commented Jan 9, 2025

Uh oh!

RickyRAV commented Jan 14, 2025

Uh oh!

vicb commented Jan 16, 2025

Uh oh!

Nopsled commented Jan 17, 2025 •

edited

Loading

Uh oh!

vicb commented Jan 29, 2025 •

edited

Loading

Uh oh!

vicb commented Jan 29, 2025 •

edited

Loading

Uh oh!

vicb commented Jan 29, 2025

Uh oh!

vicb commented Jan 30, 2025

Uh oh!

shahadpichen commented Jan 30, 2025

Uh oh!

[BUG][@opentelemetry] Could not resolve "../platform" #219

[BUG][@opentelemetry] Could not resolve "../platform" #219

Comments

NayamAmarshe commented Jan 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Describe the bug

Steps to reproduce

Expected behavior

@opennextjs/cloudflare version

Wrangler version

next info output

Additional context

dario-piotrowicz commented Jan 2, 2025

Uh oh!

This comment was marked as outdated.

shahadpichen commented Jan 8, 2025

Uh oh!

vicb commented Jan 8, 2025

Uh oh!

shahadpichen commented Jan 9, 2025

Uh oh!

RickyRAV commented Jan 14, 2025

Uh oh!

vicb commented Jan 16, 2025

Uh oh!

Nopsled commented Jan 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vicb commented Jan 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vicb commented Jan 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vicb commented Jan 29, 2025

Uh oh!

vicb commented Jan 30, 2025

Uh oh!

shahadpichen commented Jan 30, 2025

Uh oh!

NayamAmarshe commented Jan 1, 2025 •

edited

Loading

Nopsled commented Jan 17, 2025 •

edited

Loading

vicb commented Jan 29, 2025 •

edited

Loading

vicb commented Jan 29, 2025 •

edited

Loading