-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Astro v5.0.4 - [astro:db] [vite] cannot find entry point module 'astro:db' #12699
Comments
If it's any help for evidence I am also seeing this on windows 11 running node 22.12 and WSL. I am also finding the db does not seed with seed.ts. |
getting same issue on new install
|
NOTE - working when I use |
Same here "dependencies": { |
Me too,
"dependencies": {
"@astrojs/cloudflare": "^12.0.1",
"@astrojs/db": "^0.14.3",
"@astrojs/sitemap": "^3.2.1",
"@astrojs/solid-js": "^5.0.0",
"@astrojs/tailwind": "^5.1.3",
"astro": "^5.0.4",
"astro-icon": "^1.1.4",
"solid-devtools": "^0.30.1",
"solid-js": "^1.9.3",
"tailwindcss": "^3.4.16"
} It seems like everyone in here have a problem with this integration in Astro 5 right? |
Same here using: It seems Vite 6 has issues in parsing the import from |
It looks like the problem is that the fixed version of |
the same issue |
I'll try and get a patch release out today with the fixes: #12716 |
@ascorbic so the patch will be soon? |
I'll try to get it out today. |
Is this possibly related to my issue with a very basic form request?
Using this example basically verbatim: |
@jeffscottward i guess no, because db works, just a little error in console. |
I verified it's
Im totally stumped even with AI help. ---
import { db, cashOfferRequests } from "astro:db";
if (Astro.request.method === "POST") {
try {
const formData = await Astro.request.formData();
const firstName = formData.get("firstName")?.toString() ?? "";
const lastName = formData.get("lastName")?.toString() ?? "";
const email = formData.get("email")?.toString() ?? "";
if (
firstName &&
lastName &&
email
) {
await db.insert(cashOfferRequests).values({
firstName,
lastName,
email,
});
}
} catch (error) {
console.error("Error processing form submission:", error);
}
}
---
<form
id="sellForm"
method="POST"
enctype="multipart/form-data"
class="bg-[#F5F5DC] p-8 rounded-lg shadow-lg space-y-12"
> Theres something here and it's not me almost for sure. src/components/SellForm.astro
Error processing form submission: TypeError: Content-Type was not one of "multipart/form-data" or "application/x-www-form-urlencoded".
at node:internal/deps/undici/undici:5426:19
at successSteps (node:internal/deps/undici/undici:5454:27)
at consumeBody (node:internal/deps/undici/undici:5460:9)
at _Request.formData (node:internal/deps/undici/undici:5403:18)
at eval ( REDACTED marketing/src/components/SellForm.astro:19:45) |
Confirmed bug in isolated repo: |
Thanks everybody. There's no need for any more details. The fix for this is already merged. To be clear: you can safely ignore the warning. Your sites will still work. The error will disappear once we put out a release. |
Wonderful. Thanks so much @ascorbic ! |
- astro version 4 -> 5 - いくつかのビルドエラーが発生 - withastro/starlight#2658 - output の設定が変更される=> 削除:hybridレンダリングモード(https://docs.astro.build/en/guides/upgrade-to/v5/#removed-hybrid-rendering-mode) - [cannot find entry point module 'astro:db' について](withastro/astro#12699)
So glad the Astro team is on the ball like this. I ran into this bug Saturday, found this issue and decided to wait to see if it would be fixed on Monday, and it was. Big kudos |
Thankyou muchly, has also resolved my issue. |
Astro Info
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
When running
npm run dev
, I encounter an error message in the console that says:[ERROR] [astro:db] [vite] cannot find entry point module 'astro:db'.
This has been referenced in #12474, but I find that it was not fully fixed.
What's the expected result?
I expect it to not product and print that Vite error for Astro DB.
Link to Minimal Reproducible Example
cameronapak/freedom-stack#45
Participation
The text was updated successfully, but these errors were encountered: