Merging custom code after Mesh server upgrade #6413
-
Hi, I’ve kept most of my changes in separate JavaScript files, but I’ve had to modify meshcore.js to send additional information to the server for a custom scripting output page. This makes upgrading time-consuming due to merging conflicts. Is there a way to deploy a secondary meshcore.js file to devices, so I can simply reference it in the main file after upgrades instead of manually merging changes each time? Also, are there any recommendations for managing custom code and merging changes more efficiently during upgrades? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Forgot to add, in default.handlebars I renamed a few functions as they were too generic and easy to forgot what they do For example: |
Beta Was this translation helpful? Give feedback.
-
You can create .js files inside the
Check some of the modules in the folder to understand |
Beta Was this translation helpful? Give feedback.
You can create .js files inside the
modules_meshcore
folder, then require them in themeshcore.js
filerequire('custom-module');
Check some of the modules in the folder to understand