Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I am making a web application with front-end in react and back-end in Node.js. I am trying to implement role-based functionality, and I do not want users to see all the available components. For example, components for the admin tools are in component files which any user can see through the console as the browser has all the js files, but I do not want normal users to see the functionalities admin have. What can be a way to hide these components and only allow the browser to download these component files if the user role is admin.
I think server side rendering (SSR) might be the best option here. That way the content is sent from the server (safe place) and then loaded on the client after the fact.
https://www.google.com/search?q=server+side+rendering+in+react&rlz=1CDGOYI_enUS769US769&oq=server+side+rendering+in+react&aqs=chrome..69i57j0l3.8253j0j4&hl=en-US&sourceid=chrome-mobile&ie=UTF-8
You can also checkout a framework like Next.js which I believe does SSR out of the box.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
I want to show real time push notification to every user if someone started any kind off process. My project is in Angular and Node JS. If any user start some process then every user in the site should be notified by push notification
For your server side, you would need a socket solution to enable real time notification.
Since you are using NodeJs as your backend, you can try out socket.io. I personally find them quite easy to use. Their documentation can be found via their site.
https://socket.io/
If you need a step by step guide on how to combine nodeJS + socket.io + Angular, you can refer to this guide by DigitalOcean
https://www.digitalocean.com/community/tutorials/angular-socket-io
On the angular side, you need to develop a way to ensure the notification is consumed by all users. Two simple methods about this could
either be done via your state management like NGRX,
or via a global service
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
What would be the best set of technologies to use if I want to make a desktop application which would fetch data from server through JSON (node.js with MYSQL).
Side note: Currently we are using angular.js for frontend but the client wants a desktop app and is adamant. Don't want to change anything server side.
If you want to go ahead with js itself then you might want to look into electronjs you can even combine it with other frontend techs such as Angular, React or VueJs.
Another option is NW.js.
Look into both and choose as per your requirements both have pros and cons.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I have come up with various solutions like using inboxSDK or using gmail.js plugin. But are these the standard way of creating gmail extensions? Is there any another way? Can we use these plugins for production usage?
This may still depend on what you need to do with Gmail. You can use Gmail API in developing a chrome extension. You have to use chrome.identity to authorize your extension to make a request to Google APIs. You can also use gmail.js, but as stated in this related SO post this project isn't maintained by Google. You can also use Apps Script and make a web app then let your chrome extension send data through postMessage. Hope this helps.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I am new to Node js and React js. I have been given the following task.
I need to create an email sending system using Node js and React js.
The body of the email should be rich HTML and CSS and should be appear same on different mail servers like Google, Yahoo, Outlook.
So, till now I have been able to generate an express app, that is able to send emails. To get rich HTML and CSS body of the email, I am using an email template from zurb.com/ink. I am able to send a responsive email using Hogan.js .
But I am not sure of where and how to use React js?
There is no need to use React for the process you described. Unless you're designing an Front-end app to send mails.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
Understood the concepts of Redux and Node theoretically - planning to use one of them? both? not sure - How do they compare to each other ? When creating a new app (using React for Example) - can we use both of them? or one of them should be enough? I am stuck with this question. What should be the criteria here? People with expertise with these technologies, please help.
nodejs is a library for writing server-side logic in javascript.
redux is a library for managing application state, either client-side or server-side.
For example, it is possible to build an application that uses redux to manage its state on the client. This application could then communicate to a server-side api that is built using nodejs. The server-side api could also be managing its local state using redux.
So you can see that the two technologies are not mutually exclusive, it is not nodejs or redux. Instead you can choose to use them for their respective purposes separately or in conjunction.