This repository has been archived by the owner on Sep 27, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
[bug] specified file not found #52
Labels
bug
Something isn't working
Comments
Can you share the Astro.ts file? |
It is the default one generated for node when I ran the init script
…On Thu, Apr 27, 2023, 10:23 Matt Schrage ***@***.***> wrote:
Can you share the Astro.ts file?
—
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6GLF3EEFJT5Y2W2CGU5W3XDKTQFANCNFSM6AAAAAAXNK4SRU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Can you run |
@jhechtf can you install manually Deno, it seems that our auto install didnt work. What OS are you on? |
Deno is already installed on my computer, but it is a different version
than the one being downloaded.
This was run on a windows 10 machine.
Sent from mobile
…On Thu, Apr 27, 2023, 11:33 Grant G ***@***.***> wrote:
@jhechtf <https://github.com/jhechtf> can you install manually Deno, it
seems that our auto install didnt work.
What OS are you on?
—
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6GLF3RSFAMOVTLVLNFSKDXDK3XJANCNFSM6AAAAAAXNK4SRU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Currently it just requires Deno >=1.32, not specifically 1.32.5. But yeah updating it should resolve this issue, also looking into actually fixing it. |
Hopefully this commit will resolve it: a818c41 Ill create a new release soon! |
I believe this is also now resolved in https://github.com/cicadahq/cicada/tree/v0.1.48 so I am going to close the issue |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've installed the cicada CLI, and generated a file named
Astro.ts
, but this is the error i get every time.Cicada has been authorized in github.
The text was updated successfully, but these errors were encountered: