React page changes do not display

I am making changed to a React .jsx page and the changes do now show up when publishing the site. Sometimes the changes show up when running the code locally but it's sporadic.
It seems to be a caching issue.  I'm not sure how to troubleshoot this problem.
Crystal RouseTask LeadAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Julian HansenCommented:
We will need to know a lot more about the problem than what you have given us.

Some code showing the relevant bits that are involved in the mystery (along with line number references as to where we should be looking)
Expected output
Actual output

A test page showing the problem would be first prize.

Right now it is a bit too vague to nail this one down.
Shinesh PremrajanEngineering ManagerCommented:
JSX files need to be transpiled first which generates the .JS files and which is actually executed and rendered. If you need your changes to reflect as soon as you made changes then you probably need a watcher from node.js which keep eye on the file changes and transpile the file for you on adhoc basis.

In your case it seems the watcher had some issue, try running a watcher on the folder where the files are kept, so that it will do it automatically for you.

for example:  
>node tsc -- -w

Hope this helps!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Crystal RouseTask LeadAuthor Commented:
Thanks for the inputs.  I realized I didn't give enough info.  I'm new to using React.  I did figure this one out.
I wasn't setting the state for the object in question.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.