I am using AEM Non-licensed quickstart.jar to create an AEM project. I created project using Maven Archetype 15, it was build but when I created the components and styles its working, But after few days it starts giving problem after refresh styles are gone AEM dashboard is just loading. Is it because it is AEM Non-licensed version or anything else. I notice that my styles are not persistent.
Regarding the licensing: AEM does not stop working or omit styling or other developments based on a missing license. I assume that you are working with a development license. If there are any concerns with regards to your license, please reach out to your Adobe representative (e. g. the person who provided the quickstart jar to you). Anyways, this should not affect your local development from a technical point of view.
Looking at the error message that you provided in one of the answer threads:
Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.7.6:npm (npm install) on project mysite.ui.frontend: Failed to run task: 'npm install' failed. java.io.IOException: Cannot run program "C:\AEM 6.5\Projects\Ranosys Demo Site\mysite\ui.frontend\node\node.exe" (in directory "C:\AEM 6.5\Projects\Ranosys Demo Site\mysite\ui.frontend"): CreateProcess error=193, %1 is not a valid Win32 application
It seems that the build of your "mysite.ui.frontend" Maven module fails because it is not able execute Node (node.exe). If the frontend module (probably holding your styling) fails to build it could result in missing styles and the described behavior. So you should first work to fix your build. Once it runs without errors, the issue should most probably be gone.
The build process claims that node.exe used is not a valid Win32 application. Could you please double check if there is a valid executable file at "C:\AEM 6.5\Projects\Ranosys Demo Site\mysite\ui.frontend\node\node.exe"?
Maybe check if the spaces in your folder structure are causing issues here. Have you tried moving the project to a path without whitespaces (and building it there)? However, this is more of a shot into the dark. I'm not sure if this is still a thing on modern Windows environments.
Another thing to check: is there additional information (e. g. error messages or traces) when building the frontend module? Could you please share the Maven output when building that module?
If you are using AEM 220.127.116.11, then you can build a maven project using Archetype 27 which is the latest one.
Now when you say that the styles are gone when you refresh the page, is it removed automatically when you start the instance or is it after some build that was deployed to the instance.
In no case the styles will be removed automatically and the only chance is that if we deploy a build and the changes are not available as part of the code base and it was coded directly on crx/de that's the place it will be removed and the pages will break.