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

CLI: add command to check compilation without emitting files #290

Closed
folex opened this issue Sep 9, 2021 · 4 comments · Fixed by #299 or #301
Closed

CLI: add command to check compilation without emitting files #290

folex opened this issue Sep 9, 2021 · 4 comments · Fixed by #299 or #301
Assignees
Labels
cli CLI usability and bugs

Comments

@folex
Copy link
Member

folex commented Sep 9, 2021

In aqua-dht I don't need to emit .ts or .js files. But I want to have a command to make sure Aqua compiles.

Having a check command would be awesome. I'd use it as aqua check -i .

@folex folex added the cli CLI usability and bugs label Sep 9, 2021
@alari
Copy link
Member

alari commented Sep 9, 2021

Might be aqua -i ./aqua --dry or something like that, as it actually performs a dry run with a compiler backend of choice.

@folex
Copy link
Member Author

folex commented Sep 9, 2021

In rust cargo check works way faster than cargo build cuz it doesn't need to emit anything, so can optimize.

That knowledge was why I asked for a separate command, just sharing it :)

@alari
Copy link
Member

alari commented Sep 9, 2021

Yeah. I think now we can do --dry which is cheap, and optimize later :)

Now we don't have any commands for aqua, it works as a single command. This will change for sure, but I think it makes sense to add --dry earlier and then iterate on optimizations.

@folex
Copy link
Member Author

folex commented Sep 13, 2021

Aqua Compiler 0.3.1-228

> aqua -i . --dry

aqua.js -m node_modules -i . --dry

Aqua JS: Missing expected flag --output!

Seems like I can't do --dry without specifying -o

And if I do specify -o, then it will be created even though it's --dry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli CLI usability and bugs
Projects
None yet
3 participants