I tried your suggestion and I still get the error. As you’re likely aware, that folder is re-written to "C:\Users\Darren\my_workspace_202303.metadata.plugins" during the Export .war process, and the re-writing occurs the instant before I get the error. I was watching the folder during the process.
I do not have node.js or angular installed separately.
I have attached the console output text file from this attempt.
Christian:
I don’t think this matches what you’re suggesting, but it’s the only thing with ‘module’ in it - we have a Servoy Package called ‘web’ in our main solution with a utils.js containing this:
We have a custom form component that displays a button (as an image) with an associated checkbox, to be used in a list, however none of the underlying components are named ‘module’ and there’s no .js declaring any variables.
now the txt file is even weird, it does a build no errors but no output at all (after run build)
that code is just angularjs (ng1) what we talk about that building is TiNG
and yes it needs to fully recreate that directory
and then start building (remember this is purely TiNG)
but your -3 file only ends on
---- Running npm command:
C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui\node-v18.14.0-win-x64\node.exe
C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui\node-v18.14.0-win-x64\node_modules\npm\bin\npm-cli.js
run build
In dir: C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui\target\my_dist
Total time to check/install Titanium NG solution/dependencies into target folder: C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui\target\my_dist is 0 s.
and the old one does
---- Running npm command:
C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui\node-v18.14.0-win-x64\node.exe
C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui\node-v18.14.0-win-x64\node_modules\npm\bin\npm-cli.js
run build
In dir: C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui\target\my_dist
ngclient2@2023.3.0 build
ng build --configuration production --subresource-integrity=true ngclient2
‘“node”’ is not recognized as an internal or external command,
operable program or batch file.
Finished running 'run build ’ time: 0s
Total time to check/install Titanium NG solution/dependencies into target folder: C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui\target\my_dist is 6 s.
so for some reason we now even miss the error or output at all…
ngclient2@2023.3.0 build
ng build --configuration production --subresource-integrity=true ngclient2
Johan, on the chance this provides more context, I’ll attach four text files with the console output for the following:
1- Starting Developer as normal
2- Exporting .war file as normal (Export failed as before)
3- Exporting .war file after removing the C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui folder (Export failed as before)
4- Starting Developer after the error on step 3.
I’ve also included what I assume are log files related to the above noted actions, written to C:\Users\Darren\AppData\Local\npm-cache_logs. I saw a reference to those in the console output somewhere.
Not sure what else might be useful. If Christian encountered the same problem with a simple variable name, perhaps something similar is happening here with a different variable name?
Another note (that you may recall from other forum posts), is that we previously attempted an upgrade from 2020.06 to 2022.09. While we ran into other issues, we didn’t get this error and we were able to successfully export the .war file.
I’ve installed 2022.12 and am encountering the same error as 2023.03-LTS when trying to export the .war file. I’ve reinstalled 2022.09.2 and I’m able to export a .war file. So it’s something beginning in 2022.12.
I’ll continue to investigate. Hopefully someone can suggest a fix.
In case anyone is interested - I got it working. After a restart of my computer, I was getting different errors which pointing to missing files in "C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui". Not sure if that was related to the deletion of that folder at Johan’s suggestion, or if was improperly installed the first time around (during initial installation of Developer and workspace creation). So I deleted the workspace and started over from there. I restarted the computer again just in case, then attempted the .war export and it was successful.
very weird, there seems to be all kinds of right problem of maybe multiply process stuff for those things
Deleting that dir "C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui" is the same as a new workspace… (for this scenario) you just start over.
Everything thing in that dir is generated/copied into so that can be fully removed at anytime and after a restart of servoy that should be generated fully again with a node installation and the sources that are being build
very weird, there seems to be all kinds of right problem of maybe multiply process stuff for those things
Deleting that dir "C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui" is the same as a new workspace… (for this scenario) you just start over.
Everything thing in that dir is generated/copied into so that can be fully removed at anytime and after a restart of servoy that should be generated fully again with a node installation and the sources that are being build
yeah, weird. This was the error I received that prompted me to delete the entire workspace:
Error: Cannot find module ‘C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui\target\node_modules@angular\cli\bin\ng.js’
at Module._resolveFilename (node:internal/modules/cjs/loader:1047:15)
at Module._load (node:internal/modules/cjs/loader:893:27)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:23:47 {
code: ‘MODULE_NOT_FOUND’,
requireStack:
}
I restarted Developer this morning and was still able to export a .war, so it’s still working. I also remembered that I had made a copy of the C:\Users\Darren\my_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui folder before removing it at your suggestion. The
com.servoy.eclipse.ngclient.ui\target\node_modules\ folder only contained two subfolders:
.bin @angular-devkit
So, @angular\cli\bin\ng.js was already missing at that point. I must have missed that error message among the other ones. Points to an improper installation?
then some partial stuff did happen when it did install it.
If you want to fully clean it, make sure servoy is not started
delete that whole dir
and then start servoy and let it fully run
(especially the developer, it must complete one build once)
don’t delete that dir when servoy is running
FYI - I encountered the same problem after installing 2023.3.4_LTS. Deleting the \qfi_workspace_202303.metadata.plugins\com.servoy.eclipse.ngclient.ui\ folder then restarting Developer was the fix. Not sure why that folder won’t get fully populated the first time through.
if you are upgrading, then you get a second dialog (to upgrade the “server” part) and then a restart button
are you maybe restarting very soon that the ng build is still running? so it is not finished yet so you restart your developer and because of that its “half” build?
jcompagner:
if you are upgrading, then you get a second dialog (to upgrade the “server” part) and then a restart button
are you maybe restarting very soon that the ng build is still running? so it is not finished yet so you restart your developer and because of that its “half” build?
Hi Johan,
just adding to this, I think that what you said is happening a lot of the time, as I think users are not watching that the build is in progress and needs to complete before they ‘restart’…
Is there some way you can ‘delay’ the dialog about restarting until after the build has completed?
I think this will save a lot of messed up install/upgrade/updates in the future (or add some text to advise user to wait until any possible build is complete??)
Thanks
Rafi
When we first started using Servoy (2019), I tried using the upgrade option to get the latest Developer version, but it never worked. However it quickly became apparent that upgrading through Developer doesn’t fit with our development process anyways. We need to test that the new version doesn’t cause any stability problems for our deployed applications. We had a misfire when trying to upgrade to 2022.09.
So I always keep my existing instance of Developer and any upgrade involves downloading the newer version and installing it from scratch, completely separately from the last version. I allow the installation to fully complete, then begin the process of creating a workspace and adding in my projects (solutions). I’m quite sure I’m not short-circuiting the build process. Must be something else weird in my laptop, if no one else is getting the problem. I’ll just continue watching for it with each new version. At least I’ve got some sort of workaround. Thanks.