Skip to content
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

deno task dev fails due to invalid file name on Windows #493

Closed
maxmmyron opened this issue Apr 4, 2023 · 4 comments · Fixed by #494
Closed

deno task dev fails due to invalid file name on Windows #493

maxmmyron opened this issue Apr 4, 2023 · 4 comments · Fixed by #494
Assignees

Comments

@maxmmyron
Copy link
Contributor

Impressive codebase! Seems pretty deep in development but I would love to help out.

I got an interesting fail when running deno task dev resulting from the file npm:postcss-url@10.1.3 having a windows-invalid ":" character.

It seems like this is the only error of this type; replacing the colon let me run the dev server successfully.

Is there a potential path toward Renda supporting OS-independent development?

@jespertheend
Copy link
Collaborator

Hey thanks! You're my first visitor :P
Yeah ideally it should be possible to work on this on all platforms. I think the colon is an issue in https://github.com/jespertheend/deno-tsc-helper
It's been a while since I last tried to run deno task dev on windows. Let my try to figure out what's going on.

@jespertheend
Copy link
Collaborator

@maxmmyron Thanks for the report! It should be fixed now. Let me know if there's anything specific that you'd like to work on or if you need any help.

@maxmmyron
Copy link
Contributor Author

maxmmyron commented Apr 4, 2023

Just double-checked everything works with the build script, seems like it's all good! I'll make sure to check out some of the other issues.

Side note: I've been having a bit of trouble getting assets to load into the editor viewport. I was able to load and inspect the examples from source (studio/builtInAssets/gizmos/), but didn't see anything appear in the viewport.

@jespertheend
Copy link
Collaborator

For the moment Renda only has WebGPU support. You might need to enable that in your browser flags because it hasn't shipped yet. Though https://canary.renda.studio/ has a Chrome origin trial installed so you shouldn't have to change any flags there on chrome.

Other than that the onboarding is still pretty rough at the moment, and you need to create quite a bit of assets before you can get anything drawn to the screen.
I've got a minimal project right here if you want to play around with it: rendatest.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants