-
Notifications
You must be signed in to change notification settings - Fork 13
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
➕ Add Deno adapter demo (#75) #77
Conversation
Our main use case for process.env is to communicate between If I recall Arsh from the core team mentioned something about a vite global that could be used instead a while back 🤔 |
apps/astro-deno-demo/package.json
Outdated
}, | ||
"dependencies": { | ||
"@astrojs/check": "^0.5.10", | ||
"@astrojs/deno": "^5.0.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @siguici Thanks for taking on this issue! I have been out sick for the past few days and am just getting caught up with this discussion.
Not sure if you have seen either of these comments?
denoland/deno-astro-adapter#10 (comment)
denoland/deno-astro-adapter#13
Given the outdated NPM registry, might want to change this to:
"@astrojs/deno": "^5.0.1", | |
"@astrojs/deno": "github:denoland/deno-astro-adapter", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @siguici Thanks for taking on this issue! I have been out sick for the past few days and am just getting caught up with this discussion.
Not sure if you have seen either of these comments?
Wishing you a speedy recovery.
I've just seen the issue, but I don't think the problem lies there, considering that Astro's integration with Deno doesn't seem to be an issue. The problem seems to be more related to the use of environment variables. Deno doesn't support process.env.
However, I'll try to explore this way to see if it resolves the problem.
I'm aware of that, and I believe it's the only way at the moment to achieve this. Until we find a better solution.
I know it's possible to use environment variables from Vite's user configuration, but I'm not sure if there's a way to pass them globally through Vite since it's intended for frontend use and not server-side. So I think it's possible to do it in the |
Good catch @Mac-Mann! Also @siguici I reviewed the PR and it looks good! Maybe we should change the names of the demo's to: what do we think about the suggested change here? I've heard of the issues with Astro and Deno up to this point. Edit: I tried building with the proposed package change above. Build errored with:
|
@siguici think it's good to merge? Looks good to me! |
Yes, it can be merged without any issues. |
Merged :) |
I just added a demo that uses Astro's Deno adapter and I encountered no errors either for the dev script or for the build script as mentioned in #75.