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

【Feature Request】Can we use a separate graal command instead of the node command? Like deno #867

Open
alamhubb opened this issue Nov 1, 2024 · 0 comments

Comments

@alamhubb
Copy link

alamhubb commented Nov 1, 2024

Since graaljs cannot completely replace nodejs at present, we still need to use nodejs. If we use graaljs to cover nodejs, some programs will not run. When I only want to use graaljs on a certain project, using nodejs to cover graaljs is not a good choice. Can you provide a separate graaljs command? Do you also need to provide a separate graalnpm command?

Another implementation of javascript is deno, which provides a separate deno command and does not cover the node command.

At this point, another question came to my mind: why should GraalVM's GraalJS be compatible with NodeJS, instead of becoming another implementation of JS like Deno?

Just a little thought from a beginner who doesn't know much about graalvm. I hope to get a reply. I apologize if I disturb you.

@alamhubb alamhubb changed the title 【Feature Request】Can we use a separate graal command instead of the node command? 【Feature Request】Can we use a separate graal command instead of the node command? Like deno Nov 1, 2024
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

1 participant