cgatno
commented
7 years ago Node.js isn't going to go away - why would I want to remove it?! Wait....am I contradicting myself?
I know this is a little confusing now, but the project started out with a different direction and purpose than it has now. The samples hosted on the Wijmo website are formatted in a way that does not require Node.js, etc. The goal of the sample in this repo, however, is to provide a full-featured solution that also serves as a tutorial for building standalone web applications. Therefore, keeping the Node.js integration is essential and beneficial to learning more about modern web development.
A better goal for this issue is to remove Apache2 dependency. Instead, the project should use a simple Node HTTP server to serve up the sample. This would be a more fully integrated solution.
Ideally, we will be able to refactor the entire application to run without using Node.js even for development dependencies and Apache for local testing.
Apache dependency may be removed by migrating the JSON data to a local JavaScript file containing a JSON variable. This may have performance implications (look into).
As for removing dependency on Node.js and Browserify, we'll have to migrate away from CommonJS module structuring and simply use separated JS files.
It seems that a good amount of developers are familiar with ES5 import syntax and CommonJS module structure, so this really isn't a priority for the blog. It would be nice, but I think it can be explained briefly and concisely.
Any help would be much appreciated!