You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 8, 2020. It is now read-only.
We are using the generator-m-ionic for a large project that is being built into an android and ios app successfully. We are now planning to serve the same ionic-code as a website via a node.js server as well.
However, when we serve the WWW folder via node.js, the entire app.js (which has the JS code for all of our 20+ controllers) is sent to the client on serving just the login page. With substantial proprietary client side-code, we would like to only serve the login.js controller with login.html and then serve the entire app.js (for all other controllers) post successful login.
What changes would be required in the gulp configuration to achieve the same?
Thanks!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We are using the generator-m-ionic for a large project that is being built into an android and ios app successfully. We are now planning to serve the same ionic-code as a website via a node.js server as well.
However, when we serve the WWW folder via node.js, the entire app.js (which has the JS code for all of our 20+ controllers) is sent to the client on serving just the login page. With substantial proprietary client side-code, we would like to only serve the login.js controller with login.html and then serve the entire app.js (for all other controllers) post successful login.
What changes would be required in the gulp configuration to achieve the same?
Thanks!
The text was updated successfully, but these errors were encountered: