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

Support for Air command to watch files #70

Open
juanCortelezzi opened this issue May 3, 2022 · 3 comments
Open

Support for Air command to watch files #70

juanCortelezzi opened this issue May 3, 2022 · 3 comments

Comments

@juanCortelezzi
Copy link

First of all, thanks for this awesome plugin.

While using gow to run the application in watch mode works great, I believe it only works on Linux systems due to its hotkey feature. Since I may use windows from time to time, I wanted to replace it with air, which does run on both systems.

The issue was that the serve executor always passed "run" as the second argument of the command code here, which is not expected by air or almost any other file watcher.

Is it possible for this plugin to use air or any other file watcher program?

Thanks!

@adlion
Copy link

adlion commented Nov 5, 2022

I do not know your project.json configuration but I have modified mine like so and I am able to run it.

....
"serve": {
      "executor": "@nrwl/workspace:run-commands",
      "options": {
        "command": "cd apps/PROJECT_DIRECTORY && air -c .air.toml"
      }
    },

@phillipCouto
Copy link
Contributor

@beeman do you think for serve executor we can add a property to select which watcher to use?

Or maybe we should have different executors for each type? @nrwl/angular uses different executors for different servers to run the project code with hot reloaders.

What do you think?

@beeman
Copy link
Member

beeman commented Feb 11, 2023

@beeman do you think for serve executor we can add a property to select which watcher to use?

Or maybe we should have different executors for each type? @nrwl/angular uses different executors for different servers to run the project code with hot reloaders.

What do you think?

I like the idea of having various executors similar to how Nx does it. I think we can probably find a pretty clean way to implement them and I think it will be a way more constant set of tools compared to the JavaScript ecosystem.

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

4 participants