Skip to content
Source
Sign inSign up
TanStack/devtools

The requested module dayjs.min.js does not provide an export named 'default' #423

Send to my agent
Closedarolson101(GitHub profile, opens in a new tab) opened this issue 2 comments

TanStack Devtools version

0.10.2

Framework/Library version

react 19.2.5

Describe the bug and the steps to reproduce it

I have an existing project using tanstack router and tanstack query that were using the individual devtools. I followed the steps to add a TanStackDevtools component and ran into two problems:

  1. A constant loop in vite with this error. I fixed this by adding '@tanstack/devtools' to vite.config.ts optimizeDeps.exclude.
✘ [ERROR] No matching export in "node_modules/.pnpm/solid-js@1.9.7/node_modules/solid-js/web/dist/dev.js" for import "setStyleProperty"

    node_modules/.pnpm/@tanstack+devtools@0.11.2_csstype@3.2.3_solid-js@1.9.7/node_modules/@tanstack/devtools/dist/devtools/4QORE6HP.js:4:102:
      4 │ ...use, setAttribute, insert, memo, effect, className, setStyleProperty, addEventListener, style, template, classList } fro...
        ╵                                                        ~~~~~~~~~~~~~~~~


 ERROR  7:46:47 AM [vite] (client) error while updating dependencies:                                                         07:46:47
Error: Build failed with 1 error:
node_modules/.pnpm/@tanstack+devtools@0.11.2_csstype@3.2.3_solid-js@1.9.7/node_modules/@tanstack/devtools/dist/devtools/4QORE6HP.js:4:102: ERROR: No matching export in "node_modules/.pnpm/solid-js@1.9.7/node_modules/solid-js/web/dist/dev.js" for import "setStyleProperty"
    at failureErrorWithLog (/Users/andrew/GitHub/finalist/node_modules/.pnpm/esbuild@0.25.12/node_modules/esbuild/lib/main.js:1467:15)
    at /Users/andrew/GitHub/finalist/node_modules/.pnpm/esbuild@0.25.12/node_modules/esbuild/lib/main.js:926:25
    at /Users/andrew/GitHub/finalist/node_modules/.pnpm/esbuild@0.25.12/node_modules/esbuild/lib/main.js:1345:9
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
  1. this runtime error that I have not been able to bypass:
SyntaxError: The requested module '/node_modules/.pnpm/dayjs@1.11.20/node_modules/dayjs/dayjs.min.js?v=559389e5' does not provide an export named 'default' (at tree.js?v=559389e5:6:8)

the line it's pointing to is in @tanstack/devtools-ui/dist/esm/components/tree.js

import dayjs from "/node_modules/.pnpm/dayjs@1.11.20/node_modules/dayjs/dayjs.min.js?v=559389e5";

I think it has to do with the tsconfig option allowSyntheticDefaultImports which I did not previously have set, but I tried adding it (and rerunning with vite dev --force to force it to rebuild) but that did not make it work.

Sorry, I'm going through the trouble of creating a bug report, I don't have the time to also create a minimal reproducible example. Close the issue if you must.

https://github.com/TanStack/devtools/issues

Screenshots or Videos (Optional)

No response

Do you intend to try to help solve this bug with your own PR?

None

Terms & Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
  1. Thanks again for the report. Rephrasing the key triage ask clearly:

    To make this actionable, we still need a minimal reproducible example. The current repro link points to the issues list, not a runnable reproduction.

    Please share either:

    • a StackBlitz/CodeSandbox link, or
    • a small GitHub repo

    that reproduces this with the same dependency versions (@tanstack/devtools, React, Vite, and package manager), plus exact steps to run it.

    Without a debuggable repro, it’s very difficult to reliably confirm and fix the issue.

  2. ok, well, my bad. It seems the second problem was a result of the first, which was the real problem, and was the result of an older solid-js being in package.json (no idea how it got there, as I don't use solid). Taking that out made it all work correctly now.

Sign in to join this conversation.