Skip to content
This repository has been archived by the owner on Dec 10, 2024. It is now read-only.

Could not resolve "clerk:astro" #137

Open
JacobWeinbren opened this issue May 13, 2024 · 4 comments
Open

Could not resolve "clerk:astro" #137

JacobWeinbren opened this issue May 13, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@JacobWeinbren
Copy link

JacobWeinbren commented May 13, 2024

Hi -

Using the instructions you laid out on your README, I get this error. Do you know what might be causing it?

Thanks,
Jacob

[ERROR] Could not resolve "clerk:astro"

   node_modules/astro-clerk-auth/dist/chunk-DUP22WC7.js:26:38:
     26 │ import { getClerkAuthInitState } from "clerk:astro";
        ╵                                       ~~~~~~~~~~~~~

 You can mark the path "clerk:astro" as external to exclude it from the bundle, which will remove
 this error and leave the unresolved path in the bundle.

05:36:33 [ERROR] [vite] error while updating dependencies:
Error: Build failed with 1 error:
node_modules/astro-clerk-auth/dist/chunk-DUP22WC7.js:26:38: ERROR: Could not resolve "clerk:astro"
   at failureErrorWithLog (/Users/jacobweinbren/Documents/GitHub/Mappa/node_modules/vite/node_modules/esbuild/lib/main.js:1651:15)
   at /Users/jacobweinbren/Documents/GitHub/Mappa/node_modules/vite/node_modules/esbuild/lib/main.js:1059:25
   at /Users/jacobweinbren/Documents/GitHub/Mappa/node_modules/vite/node_modules/esbuild/lib/main.js:1527:9
   at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
@panteliselef panteliselef self-assigned this May 13, 2024
@panteliselef panteliselef added the bug Something isn't working label May 13, 2024
@panteliselef
Copy link
Owner

Hey @JacobWeinbren thanks for reporting this. Could you try v0.5.0, while i investigate ?

@ian-pascoe
Copy link

I am having the same issue. I will switch to 0.5.0 for the time being.

@panteliselef
Copy link
Owner

I've confirmed the issue and i'm working on a solution

@panteliselef
Copy link
Owner

I've reverted the changes that were causing this issue with [email protected].

I'm leaving this open as I plan to come back to the previous solution and fix the core issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants