Yarn start --sources packages/ems-active-visits-app failed to run on browser

Development
1 
PS C:\Users\user\frontend modules 03\openmrs-esm-patient-management>  yarn start --openmrs-esm-patient-management/ems-active-visits-app

━━━ Yarn Package Manager - 4.10.3 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  $ yarn <command>

You can also print more details about any of these commands by calling them with
the `-h,--help` flag right after the command name.

after installing all the dependencies,and commanding yarn,the dev server failed to run. can someone help me with the right approach .

2

The command in your title looks right, but the command in the text below doesn’t. It seems to be missing the sources part.

3

it’s really bringing this PS C:\Users\user\frontend modules 03\openmrs-esm-patient-management> yarn start sources packages/openmrs-esm-patient-management/esm-active-visits-app

Usage Error: Missing source for the plugin.js plugin - please try to remove the plugin from .yarnrc.yml then reinstall it manually. This error usually occurs because .gitignore is incorrect, check Questions & Answers | Yarn to make sure your plugin folder isn’t gitignored.

━━━ Yarn Package Manager - 4.10.3 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

$ yarn

You can also print more details about any of these commands by calling them with the -h,--help flag right after the command name.

4

I replied on Slack, but there’s nothing in the default Yarn configuration for the patient management module that references a “plugin.js”. If you have local changes to that file, revert them.

5

yes have reverted the changes but still seems to be the same thing when even working with a different project as well. Actually i have tried using gitbash and command prompt,but still same work result. PS C:\Users\user\openmrs core> yarn start --sources’packages/esm-login-app,’ yarn run v1.22.22 warning package.json: No license field error Command “start” not found. info Visit yarn run | Yarn for documentation about this command. Really wondering what could be the mistake?

6

most probably a syntax error due to the configuration of your package.json.
double check your package.json to see which arguments to use.