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

spack issues #44

Closed
lastmjs opened this issue Mar 10, 2022 · 5 comments
Closed

spack issues #44

lastmjs opened this issue Mar 10, 2022 · 5 comments

Comments

@lastmjs
Copy link
Member

lastmjs commented Mar 10, 2022

We need these types of issues to be resolved so that imports work perfectly no matter where they are located and whether or not they are written in TypeScript:

@lastmjs
Copy link
Member Author

lastmjs commented Mar 15, 2022

I've moved on to esbuild for now, which is working great. Apparently spack isn't really ready for prime time

@lastmjs lastmjs closed this as completed Mar 15, 2022
@georgekrax
Copy link

I believe this is a general issue about Spack, and should not be closed. Other developers seem to face similar struggles, which should be fixed. If you have found a new solution or anything related to it, please feel free to comment here!

@lastmjs
Copy link
Member Author

lastmjs commented Mar 15, 2022

Hey, I'm not sure if you're commenting in the correct repo. The issues above are still open in the spack repo, this is just the Azle TypeScript CDK for the Internet Computer, which will no longer use spack

@georgekrax
Copy link

@lastmjs Oh my bad 😅. You are right, do you have the link for the issue in the swc-project repo?

@lastmjs
Copy link
Member Author

lastmjs commented Mar 15, 2022

No problem! Both of the issues are linked here: #44 (comment)

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

No branches or pull requests

2 participants