npm run watch not change screen

Hi ​@bihalivan15,
 

If npm run watch --- --env customFolder=development screenIds="TR300300" completes successfully, but the changes are reflected only after publishing the customization project, I would first verify the development setup rather than the code itself.

Make sure the customFolder is pointing to the same Acumatica instance that you are testing in the browser. Also check whether the change is a client-side change or a server-side customization.

For JavaScript/UI changes, clear the browser cache and perform a hard refresh. the watch process alone will not activate the compiled customization in the running Acumatica instance; the customization needs to be deployed/published through the appropriate development workflow.
You can use below command to your FrontendSources\screen folder.
npm run build-dev --- --env customFolder=development screenIds=TR300300

I would also verify the generated files under the development custom folder and confirm that TR300300 is actually being included by the watch process.

If publishing makes the change visible consistently, that is a good indication that the watch output is not being loaded by the instance you are testing against, or the change requires server-side deployment.

Using watch isn’t recommended just because it will be compiling on each save automatically. You probably want to confirm when you want to compile yourself.

From within ‘...FrontendSources\screen’ use:

npm run build-dev --- --env customFolder=development screenIds=TR300300

If you have published, there are copies of your compiled screen that need to be removed before you can see your development changes. See the following comment:

In your case you’ll want to delete:

Scripts/Screens/<Tenant Name>/TR300300.html
Scripts/Screens/<Tenant Name>/TR300300.*.bundle.js
App_Data/TSScreenInfo/<Tenant Name>/TR300300.json

After that, you can use the npm run build-dev command to compile the screen and immediately see your changes.

I don't think the 'watch' command is the issue. It's probably that you already have MUI files published and the ones you're building aren't taking effect. This is a known issue with MUI development. You'll have to either remove the MUI files from the package before publishing or manually remove them from \customizationScreen\