Changes to Kibana are not picked up when developing third party plugins

[spalger]

Hi,

Concerning developer experience pain, I would like to say that since Kibana 7.8.0, I don't have anymore core code hot reload.
I do yarn start, and if I change something in core code, I need to restart fully Kibana so that my change is applied. That's somewhat painful :(
Before Kibana 7.8.0, I didn't have this issue.

Originally posted by @fbaligand in #70733 (comment)

@fbaligand would you mind adding some reproduction steps here so that I can dig into this? yarn start runs Kibana in a mode where everything should be watched correctly, but but it's unclear what's not working and what directory you're executing yarn start in for instance.

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[fbaligand]

Hi,

Thanks to have open a dedicated issue for that.
Then, here are some precisions:

• I run exactly this command: yarn start --oss --no-watch
• I get the issue on v7.8.0 tag
• wether I run this command in my plugin directory ($KIBANA_HOME/plugins/enhanced-table) or directly in kibana home, I get the issue
• strangely, changes in my plugin are taken hot way, but not kibana core code changes.
• I reproduce also the issue on master branch (with no community plugin at all)
• I run on Windows 10 OS.

I hope that I gave you enough details.

[tylersmalley]

Sorry for the delay on this --no-watch applies to the optimizer, so this would be why the plugin isn't being updated. Removing that option should resolve this issue.

Please reopen this is still an issue after removing the flag.

[fbaligand]

Thanks for the answer.
I confirm that I don't use --no-watch parameter anymore, and it works fine.