-
Notifications
You must be signed in to change notification settings - Fork 45
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
npm install fail #4
Comments
Hello! @jtenner, author of as-pect has since deleted the By the way, this project doesn't render anything on the screen yet (that's what we're aiming for of course). It currently runs unit tests for the classes we've finished so far. But it would be great if you want to contribute. Thanks for checking it out! If I don't get to it first, @jtenner, would you be open to make a PR to bring this up to date with as-pect from NPM? I'd like to swing back to this soon after some other stuff in my life calms down. Or @liveme, if you'd like to give it a try, glas needs to be updated to using these packages:
|
I switched to a mono repo to get more organized about how aspect worked. I could probably help with a pull request if you needed it. |
That would be great! I'm sure the changes aren't much, but you'd know best. What was working before was |
This is unfortunate. When I tried to run latest AssemblyScript and latest @as-pect/cli together, I found a compile-time error.
This is going to take some time and an update. Sorry for the trouble. |
@jtenner Just gave it a shot, and everything is working! Nice! I've updated assemblyscript and as-pect, and added continuous integration (too easy with GitHub Actions). Not sure how the build passed though, as the CI pull request doesn't have the updated dependencies. Hmmm, well let me get the first PR merged. |
Alright @liveme, it is good to go. If you'd like to grab any class from the Three.js repository along with its unit tests, and port it to AssemblyScript, that'd be awesome. It'll be some time before it renders anything. The hardest part will be porting over At present, the |
If you get this error update node to 14.x |
It make an error when I run
npm install
:npm ERR! code 1 npm ERR! Command failed: git checkout runtime npm ERR! error: pathspec 'runtime' did not match any file(s) known to git.
Using
yarn install
also prompts for failure:error Couldn't find match for "runtime" in "refs/heads/2.4.2,refs/heads/asc_to_devDep,refs/heads/fix_ts_output,refs/heads/greenkeeper/ts-jest-24.1.0,refs/heads/greenkeeper/ts-jest-pin-24.0.2,refs/heads/master,refs/heads/v2.2.1,refs/heads/v2.3.2,refs/heads/v2.3.3,refs/heads/v2.4.1.0,refs/pull/100/head,refs/pull/...
The text was updated successfully, but these errors were encountered: