Difference between revisions of "Our SPA"
From Organic Design wiki
(Webpack noob intro) |
(see also) |
||
| Line 5: | Line 5: | ||
On the client side we use the [[VueJS]] framework for templating and component model with the [https://router.vuejs.org Vue router] and [https://vuex.vuejs.org Vuex storage layer]. Vue uses [https://webpack.js.org/ WebpackJS] (see also [https://dev.to/nitishdayal/stages-of-learning-webpack-pt-2---the-config this] noob intro) to integrate more tightly with NodeJS and it's build process. | On the client side we use the [[VueJS]] framework for templating and component model with the [https://router.vuejs.org Vue router] and [https://vuex.vuejs.org Vuex storage layer]. Vue uses [https://webpack.js.org/ WebpackJS] (see also [https://dev.to/nitishdayal/stages-of-learning-webpack-pt-2---the-config this] noob intro) to integrate more tightly with NodeJS and it's build process. | ||
| + | |||
| + | == See also == | ||
| + | *[[VueJS]] | ||
| + | *[[NodeJS]] | ||
| + | *[[JavaScript]] | ||
Revision as of 14:51, 27 July 2017
We're currently working in a number of apps which are in the form of a Single Page Application. This article describes the common SPA structure we're using for such projects.
Technology stack
Our system uses NodeJS on the server side with FeathersJS for authentication (using ExpressJS) and real-time bidirectional communications (using SocketIO). We use MongoDB for our no-SQL database layer and Mongoose to integrate it with NodeJS.
On the client side we use the VueJS framework for templating and component model with the Vue router and Vuex storage layer. Vue uses WebpackJS (see also this noob intro) to integrate more tightly with NodeJS and it's build process.
