-
Notifications
You must be signed in to change notification settings - Fork 166
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
Uncaught TypeError in Getting Started guide #302
Comments
I have the exact same issue with same system info (mac os 11.3.1) |
This isn't a bug looking more into it. afaik 0.2.28 is not compatable with any newer Deno versions and only works with Deno 1.6.x. If you want to use Deno 1.8.0 use the latest alpha version of Aleph. |
I downgraded deno version to 1.6.3 and the error persists:
|
@ajcwebdev did you fix the issue on your side? If yes, could you please share what you've done? |
Hey @augustomallmann, unfortunately I have not had time to debug, been busy with work. I'm not sure if anyone on the Aleph team is in the Deno Discord but you could probably get some assistance there. |
It seems then that this is an issue with esm.sh then, though i don't know for sure (cc @ije) PS: you can also join the aleph discord server for help, but I am also in the deno discord server if you need help with stuff |
I think it's to strict typescript check, type any not allowed any more then we must type returned value of each function/method |
Same error on a fresh project:
|
With 0.33-alpha
|
Hi, I just tried using this framework in case if you are also in the same boat, please upgrade your I forgot which command to upgrade my aleph version tho try |
Hi @thesabbir, have you found a solution for this? Thanks in advance |
@ije Do you think we could include this in the first 0.3 beta? |
I found a potential fix for deno 1.10 / aleph 0.3.0-alpha.33 : I reinstalled aleph 0.3.0-alpha.33 with an additional dummy --location flag, like this:
And it finally worked -- localStorage is finally operational. |
Documentation is way behind on things. @scally good job! |
@thesabbir I would like to point out that the doc is purposely not updated with alpha stuff, well, because its alpha and super unstable compared to 0.2.28. @scally Awesome! |
I think most people who are going to be finding the getting started guide are going to be on a recent version of Deno and are going to assume that they can just run the commands and get started. If this is not the case there should be more thorough instructions to get your dev environment setup. |
@ajcwebdev No offense to them, but they are probably rushing then and not paying attention to the documentation since its still clearly listed that the Deno version to use 1.6.3 |
Most Node developers use tools like NVM to handle their Node versioning, is there a similar tool for Deno? How would you get onto Deno 1.6.3? |
@ajcwebdev You would just downgrade to Deno 1.6.3. There isn't any tool afaik that can do something like nvm, you would just have to downgrade to Deno 1.6.3 if you want to use the latest somewhat stable Aleph version. |
Cool, thanks for the info @shadowtime2000! 👍 Haven't tried it yet but it looks like there is in fact a dvm. |
I know this issue was closed, but I feel like most people would assume that a minor version difference wouldn't cause a breaking discrepancy like this. Is the necessity for the |
The reason you wouldn't expect that is that Maven is (iirc) stable. Aleph.js is not. We are in the early stages of the project, and so it should be expected that breaking changes will come. Idk if you would really consider this even technically a bug in Deno because it seems to be kind of expected with requiring a Lmk what you think though. |
I figured this would come up and I can accept that. However, I really meant for Maven to be the analogue of Deno, while Spring would be the analogue of Aleph.js. I meant to convey that I find it strange that a Deno minor increment would break the 'Getting Started' workflow as documented for Aleph.js. However, reading through the issues around the |
Hello Aleph.js team 👋. I was recently updating my blog post about Aleph and found that I was getting an error when following along with the current Getting Started guide. All three
aleph
commands,dev
,start
, andbuild
result in the same error.Commands entered:
Error output:
Aleph version
Deno version
deno info
My system info
Hopefully that's helpful, let me know if you need other system info or anything like that.
The text was updated successfully, but these errors were encountered: