Alternatives to Electron logo

Alternatives to Electron

Photon, React Native Desktop, React Native, React, and JavaScript are the most popular alternatives and competitors to Electron.
11.5K
10K
+ 1
148

What is Electron and what are its top alternatives?

With Electron, creating a desktop application for your company or idea is easy. Initially developed for GitHub's Atom editor, Electron has since been used to create applications by companies like Microsoft, Facebook, Slack, and Docker. The Electron framework lets you write cross-platform desktop applications using JavaScript, HTML and CSS. It is based on io.js and Chromium and is used in the Atom editor.
Electron is a tool in the Cross-Platform Desktop Development category of a tech stack.
Electron is an open source tool with GitHub stars and GitHub forks. Here’s a link to Electron's open source repository on GitHub

Top Alternatives to Electron

  • Photon
    Photon

    The fastest way to build beautiful Electron apps using simple HTML and CSS. Underneath it all is Electron. Originally built for GitHub's Atom text editor, Electron is the easiest way to build cross-platform desktop applications. ...

  • React Native Desktop
    React Native Desktop

    Build OS X desktop apps using React Native.

  • React Native
    React Native

    React Native enables you to build world-class application experiences on native platforms using a consistent developer experience based on JavaScript and React. The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • Python
    Python

    Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best. ...

  • Node.js
    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

  • HTML5
    HTML5

    HTML5 is a core technology markup language of the Internet used for structuring and presenting content for the World Wide Web. As of October 2014 this is the final and complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). The previous version, HTML 4, was standardised in 1997. ...

Electron alternatives & related posts

Photon logo

Photon

30
0
Framework for Electron apps
30
0
PROS OF PHOTON
    Be the first to leave a pro
    CONS OF PHOTON
      Be the first to leave a con

      related Photon posts

      React Native Desktop logo

      React Native Desktop

      15
      11
      React Native for OS X
      15
      11
      PROS OF REACT NATIVE DESKTOP
      • 3
        Pretty awesome
      • 2
        Is native app
      • 2
        Does not include any browser
      • 2
        Memory usage reduced
      • 1
        Quickly convert react.js web app to desktop app
      • 1
        Open source
      CONS OF REACT NATIVE DESKTOP
      • 0
        Memory usage reduced

      related React Native Desktop posts

      React Native logo

      React Native

      34.1K
      1.2K
      A framework for building native apps with React
      34.1K
      1.2K
      PROS OF REACT NATIVE
      • 214
        Learn once write everywhere
      • 174
        Cross platform
      • 169
        Javascript
      • 122
        Native ios components
      • 69
        Built by facebook
      • 66
        Easy to learn
      • 46
        Bridges me into ios development
      • 40
        It's just react
      • 39
        No compile
      • 36
        Declarative
      • 22
        Fast
      • 13
        Virtual Dom
      • 12
        Livereload
      • 12
        Insanely fast develop / test cycle
      • 11
        Great community
      • 9
        Easy setup
      • 9
        Backed by Facebook
      • 9
        Native android components
      • 9
        It is free and open source
      • 7
        Scalable
      • 7
        Highly customizable
      • 6
        Awesome
      • 6
        Great errors
      • 6
        Win win solution of hybrid app
      • 6
        Everything component
      • 5
        Not dependent on anything such as Angular
      • 5
        Simple
      • 4
        OTA update
      • 4
        Awesome, easy starting from scratch
      • 3
        Easy to use
      • 3
        As good as Native without any performance concerns
      • 2
        Over the air update (Flutter lacks)
      • 2
        Can be incrementally added to existing native apps
      • 2
        Hot reload
      • 2
        Web development meets Mobile development
      • 2
        'It's just react'
      • 2
        Many salary
      • 1
        Ngon
      CONS OF REACT NATIVE
      • 23
        Javascript
      • 19
        Built by facebook
      • 12
        Cant use CSS
      • 4
        30 FPS Limit
      • 2
        Slow
      • 2
        Generate large apk even for a simple app
      • 2
        Some compenents not truly native

      related React Native posts

      Collins Ogbuzuru
      Front-end dev at Evolve credit · | 57 upvotes · 380K views

      Your tech stack is solid for building a real-time messaging project.

      React and React Native are excellent choices for the frontend, especially if you want to have both web and mobile versions of your application share code.

      ExpressJS is an unopinionated framework that affords you the flexibility to use it's features at your term, which is a good start. However, I would recommend you explore Sails.js as well. Sails.js is built on top of Express.js and it provides additional features out of the box, especially the Websocket integration that your project requires.

      Don't forget to set up Graphql codegen, this would improve your dev experience (Add Typescript, if you can too).

      I don't know much about databases but you might want to consider using NO-SQL. I used Firebase real-time db and aws dynamo db on a few of my personal projects and I love they're easy to work with and offer more flexibility for a chat application.

      See more
      dagim debebe

      Hi,

      I am a student and a junior developer who is a graduating candidate in comp sci major. I am about to start building my final year project which is a real-time messaging application for software developers to Enhance Knowledge Exchange and Problem Solving. It is mainly a chat application with more enhanced features. I am planning to use React and React Native for the frontend and cross-platform mobile apps, Node.js and ExpressJS for the backend, GraphQL for fetching and manipulating data from the backend and PostgreSQL for the database, and finally Socket.IO for the real-time chatting and communication. I would highly appreciate it if anyone here with experience in building similar apps to tell me if I made a good choice or suggest better tech stacks.

      Thanks in advance.

      See more
      React logo

      React

      176.7K
      4.1K
      A JavaScript library for building user interfaces
      176.7K
      4.1K
      PROS OF REACT
      • 837
        Components
      • 673
        Virtual dom
      • 579
        Performance
      • 509
        Simplicity
      • 442
        Composable
      • 186
        Data flow
      • 166
        Declarative
      • 128
        Isn't an mvc framework
      • 120
        Reactive updates
      • 115
        Explicit app state
      • 50
        JSX
      • 29
        Learn once, write everywhere
      • 22
        Easy to Use
      • 22
        Uni-directional data flow
      • 18
        Works great with Flux Architecture
      • 11
        Great perfomance
      • 10
        Javascript
      • 9
        Built by Facebook
      • 8
        TypeScript support
      • 6
        Speed
      • 6
        Server Side Rendering
      • 6
        Scalable
      • 5
        Excellent Documentation
      • 5
        Functional
      • 5
        Easy as Lego
      • 5
        Closer to standard JavaScript and HTML than others
      • 5
        Cross-platform
      • 5
        Awesome
      • 5
        Hooks
      • 5
        Easy to start
      • 5
        Feels like the 90s
      • 5
        Props
      • 4
        Fancy third party tools
      • 4
        Allows creating single page applications
      • 4
        Sdfsdfsdf
      • 4
        Start simple
      • 4
        Strong Community
      • 4
        Super easy
      • 4
        Server side views
      • 4
        Scales super well
      • 3
        Every decision architecture wise makes sense
      • 3
        Has arrow functions
      • 3
        Rich ecosystem
      • 3
        Very gentle learning curve
      • 3
        Beautiful and Neat Component Management
      • 3
        Just the View of MVC
      • 3
        Simple, easy to reason about and makes you productive
      • 3
        Fast evolving
      • 3
        SSR
      • 3
        Great migration pathway for older systems
      • 3
        Simple
      • 3
        Has functional components
      • 2
        Fragments
      • 2
        Split your UI into components with one true state
      • 2
        HTML-like
      • 2
        Image upload
      • 2
        Recharts
      • 2
        Permissively-licensed
      • 2
        Sharable
      • 1
        React hooks
      • 1
        Datatables
      CONS OF REACT
      • 41
        Requires discipline to keep architecture organized
      • 30
        No predefined way to structure your app
      • 29
        Need to be familiar with lots of third party packages
      • 13
        JSX
      • 10
        Not enterprise friendly
      • 6
        One-way binding only
      • 3
        State consistency with backend neglected
      • 3
        Bad Documentation
      • 2
        Error boundary is needed
      • 2
        Paradigms change too fast

      related React posts

      Johnny Bell

      I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

      I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

      I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

      Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

      Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

      With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

      If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

      See more
      Collins Ogbuzuru
      Front-end dev at Evolve credit · | 57 upvotes · 380K views

      Your tech stack is solid for building a real-time messaging project.

      React and React Native are excellent choices for the frontend, especially if you want to have both web and mobile versions of your application share code.

      ExpressJS is an unopinionated framework that affords you the flexibility to use it's features at your term, which is a good start. However, I would recommend you explore Sails.js as well. Sails.js is built on top of Express.js and it provides additional features out of the box, especially the Websocket integration that your project requires.

      Don't forget to set up Graphql codegen, this would improve your dev experience (Add Typescript, if you can too).

      I don't know much about databases but you might want to consider using NO-SQL. I used Firebase real-time db and aws dynamo db on a few of my personal projects and I love they're easy to work with and offer more flexibility for a chat application.

      See more
      JavaScript logo

      JavaScript

      368.8K
      8.1K
      Lightweight, interpreted, object-oriented language with first-class functions
      368.8K
      8.1K
      PROS OF JAVASCRIPT
      • 1.7K
        Can be used on frontend/backend
      • 1.5K
        It's everywhere
      • 1.2K
        Lots of great frameworks
      • 899
        Fast
      • 746
        Light weight
      • 425
        Flexible
      • 392
        You can't get a device today that doesn't run js
      • 286
        Non-blocking i/o
      • 237
        Ubiquitousness
      • 191
        Expressive
      • 55
        Extended functionality to web pages
      • 49
        Relatively easy language
      • 46
        Executed on the client side
      • 30
        Relatively fast to the end user
      • 25
        Pure Javascript
      • 21
        Functional programming
      • 15
        Async
      • 13
        Full-stack
      • 12
        Its everywhere
      • 12
        Future Language of The Web
      • 12
        Setup is easy
      • 11
        Because I love functions
      • 11
        JavaScript is the New PHP
      • 10
        Like it or not, JS is part of the web standard
      • 9
        Expansive community
      • 9
        Everyone use it
      • 9
        Can be used in backend, frontend and DB
      • 9
        Easy
      • 8
        Most Popular Language in the World
      • 8
        Easy to hire developers
      • 8
        Powerful
      • 8
        Can be used both as frontend and backend as well
      • 8
        For the good parts
      • 8
        No need to use PHP
      • 7
        Its fun and fast
      • 7
        Popularized Class-Less Architecture & Lambdas
      • 7
        Agile, packages simple to use
      • 7
        Supports lambdas and closures
      • 7
        Love-hate relationship
      • 7
        Photoshop has 3 JS runtimes built in
      • 7
        Evolution of C
      • 7
        Hard not to use
      • 7
        Versitile
      • 7
        Nice
      • 7
        It's fun
      • 6
        1.6K Can be used on frontend/backend
      • 6
        Client side JS uses the visitors CPU to save Server Res
      • 6
        It let's me use Babel & Typescript
      • 6
        Can be used on frontend/backend/Mobile/create PRO Ui
      • 6
        Easy to make something
      • 5
        Clojurescript
      • 5
        What to add
      • 5
        Scope manipulation
      • 5
        Function expressions are useful for callbacks
      • 5
        Stockholm Syndrome
      • 5
        Promise relationship
      • 5
        Client processing
      • 5
        Everywhere
      • 4
        Because it is so simple and lightweight
      • 4
        Only Programming language on browser
      • 1
        Not the best
      • 1
        Test
      • 1
        Easy to learn and test
      • 1
        Subskill #4
      • 1
        Easy to understand
      • 1
        Love it
      • 1
        Hard to learn
      • 1
        Easy to learn
      • 1
        Test2
      • 0
        Hard 彤
      CONS OF JAVASCRIPT
      • 22
        A constant moving target, too much churn
      • 20
        Horribly inconsistent
      • 15
        Javascript is the New PHP
      • 9
        No ability to monitor memory utilitization
      • 8
        Shows Zero output in case of ANY error
      • 7
        Thinks strange results are better than errors
      • 6
        Can be ugly
      • 3
        No GitHub
      • 2
        Slow
      • 0
        HORRIBLE DOCUMENTS, faulty code, repo has bugs

      related JavaScript posts

      Zach Holman

      Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

      But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

      But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

      Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

      See more
      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 13.3M views

      How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

      Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

      Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

      https://eng.uber.com/distributed-tracing/

      (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

      Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

      See more
      Python logo

      Python

      249.1K
      6.9K
      A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
      249.1K
      6.9K
      PROS OF PYTHON
      • 1.2K
        Great libraries
      • 965
        Readable code
      • 848
        Beautiful code
      • 789
        Rapid development
      • 692
        Large community
      • 439
        Open source
      • 394
        Elegant
      • 283
        Great community
      • 274
        Object oriented
      • 222
        Dynamic typing
      • 78
        Great standard library
      • 62
        Very fast
      • 56
        Functional programming
      • 52
        Easy to learn
      • 47
        Scientific computing
      • 36
        Great documentation
      • 30
        Productivity
      • 29
        Matlab alternative
      • 29
        Easy to read
      • 25
        Simple is better than complex
      • 21
        It's the way I think
      • 20
        Imperative
      • 19
        Very programmer and non-programmer friendly
      • 19
        Free
      • 17
        Powerfull language
      • 17
        Machine learning support
      • 16
        Fast and simple
      • 14
        Scripting
      • 12
        Explicit is better than implicit
      • 11
        Ease of development
      • 10
        Clear and easy and powerfull
      • 9
        Unlimited power
      • 8
        It's lean and fun to code
      • 8
        Import antigravity
      • 7
        Print "life is short, use python"
      • 7
        Python has great libraries for data processing
      • 6
        Although practicality beats purity
      • 6
        Fast coding and good for competitions
      • 6
        There should be one-- and preferably only one --obvious
      • 6
        High Documented language
      • 6
        Readability counts
      • 6
        Rapid Prototyping
      • 6
        I love snakes
      • 6
        Now is better than never
      • 6
        Flat is better than nested
      • 6
        Great for tooling
      • 5
        Great for analytics
      • 5
        Web scraping
      • 5
        Lists, tuples, dictionaries
      • 4
        Complex is better than complicated
      • 4
        Socially engaged community
      • 4
        Plotting
      • 4
        Beautiful is better than ugly
      • 4
        Easy to learn and use
      • 4
        Easy to setup and run smooth
      • 4
        Simple and easy to learn
      • 4
        Multiple Inheritence
      • 4
        CG industry needs
      • 3
        List comprehensions
      • 3
        Powerful language for AI
      • 3
        Flexible and easy
      • 3
        It is Very easy , simple and will you be love programmi
      • 3
        Many types of collections
      • 3
        If the implementation is easy to explain, it may be a g
      • 3
        If the implementation is hard to explain, it's a bad id
      • 3
        Special cases aren't special enough to break the rules
      • 3
        Pip install everything
      • 3
        No cruft
      • 3
        Generators
      • 3
        Import this
      • 2
        Can understand easily who are new to programming
      • 2
        Securit
      • 2
        Should START with this but not STICK with This
      • 2
        A-to-Z
      • 2
        Because of Netflix
      • 2
        Only one way to do it
      • 2
        Better outcome
      • 2
        Good for hacking
      • 2
        Batteries included
      • 2
        Procedural programming
      • 1
        Sexy af
      • 1
        Automation friendly
      • 1
        Slow
      • 1
        Best friend for NLP
      • 0
        Powerful
      • 0
        Keep it simple
      • 0
        Ni
      CONS OF PYTHON
      • 53
        Still divided between python 2 and python 3
      • 28
        Performance impact
      • 26
        Poor syntax for anonymous functions
      • 22
        GIL
      • 19
        Package management is a mess
      • 14
        Too imperative-oriented
      • 12
        Hard to understand
      • 12
        Dynamic typing
      • 12
        Very slow
      • 8
        Indentations matter a lot
      • 8
        Not everything is expression
      • 7
        Incredibly slow
      • 7
        Explicit self parameter in methods
      • 6
        Requires C functions for dynamic modules
      • 6
        Poor DSL capabilities
      • 6
        No anonymous functions
      • 5
        Fake object-oriented programming
      • 5
        Threading
      • 5
        The "lisp style" whitespaces
      • 5
        Official documentation is unclear.
      • 5
        Hard to obfuscate
      • 5
        Circular import
      • 4
        Lack of Syntax Sugar leads to "the pyramid of doom"
      • 4
        The benevolent-dictator-for-life quit
      • 4
        Not suitable for autocomplete
      • 2
        Meta classes
      • 1
        Training wheels (forced indentation)

      related Python posts

      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 13.3M views

      How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

      Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

      Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

      https://eng.uber.com/distributed-tracing/

      (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

      Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

      See more
      Nick Parsons
      Building cool things on the internet 🛠️ at Stream · | 35 upvotes · 4.4M views

      Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

      We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

      We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

      Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

      #FrameworksFullStack #Languages

      See more
      Node.js logo

      Node.js

      192.1K
      8.5K
      A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
      192.1K
      8.5K
      PROS OF NODE.JS
      • 1.4K
        Npm
      • 1.3K
        Javascript
      • 1.1K
        Great libraries
      • 1K
        High-performance
      • 805
        Open source
      • 487
        Great for apis
      • 477
        Asynchronous
      • 425
        Great community
      • 390
        Great for realtime apps
      • 296
        Great for command line utilities
      • 86
        Websockets
      • 84
        Node Modules
      • 69
        Uber Simple
      • 59
        Great modularity
      • 58
        Allows us to reuse code in the frontend
      • 42
        Easy to start
      • 35
        Great for Data Streaming
      • 32
        Realtime
      • 28
        Awesome
      • 25
        Non blocking IO
      • 18
        Can be used as a proxy
      • 17
        High performance, open source, scalable
      • 16
        Non-blocking and modular
      • 15
        Easy and Fun
      • 14
        Easy and powerful
      • 13
        Future of BackEnd
      • 13
        Same lang as AngularJS
      • 12
        Fullstack
      • 11
        Fast
      • 10
        Scalability
      • 10
        Cross platform
      • 9
        Simple
      • 8
        Mean Stack
      • 7
        Great for webapps
      • 7
        Easy concurrency
      • 6
        Typescript
      • 6
        Fast, simple code and async
      • 6
        React
      • 6
        Friendly
      • 5
        Control everything
      • 5
        Its amazingly fast and scalable
      • 5
        Easy to use and fast and goes well with JSONdb's
      • 5
        Scalable
      • 5
        Great speed
      • 5
        Fast development
      • 4
        It's fast
      • 4
        Easy to use
      • 4
        Isomorphic coolness
      • 3
        Great community
      • 3
        Not Python
      • 3
        Sooper easy for the Backend connectivity
      • 3
        TypeScript Support
      • 3
        Blazing fast
      • 3
        Performant and fast prototyping
      • 3
        Easy to learn
      • 3
        Easy
      • 3
        Scales, fast, simple, great community, npm, express
      • 3
        One language, end-to-end
      • 3
        Less boilerplate code
      • 2
        Npm i ape-updating
      • 2
        Event Driven
      • 2
        Lovely
      • 1
        Creat for apis
      • 0
        Node
      CONS OF NODE.JS
      • 46
        Bound to a single CPU
      • 45
        New framework every day
      • 40
        Lots of terrible examples on the internet
      • 33
        Asynchronous programming is the worst
      • 24
        Callback
      • 19
        Javascript
      • 11
        Dependency hell
      • 11
        Dependency based on GitHub
      • 10
        Low computational power
      • 7
        Very very Slow
      • 7
        Can block whole server easily
      • 7
        Callback functions may not fire on expected sequence
      • 4
        Breaking updates
      • 4
        Unstable
      • 3
        Unneeded over complication
      • 3
        No standard approach
      • 1
        Bad transitive dependency management
      • 1
        Can't read server session

      related Node.js posts

      Anurag Maurya

      Needs advice on code coverage tool in Node.js/ExpressJS with External API Testing Framework

      Hello community,

      I have a web application with the backend developed using Node.js and Express.js. The backend server is in one directory, and I have a separate API testing framework, made using SuperTest, Mocha, and Chai, in another directory. The testing framework pings the API, retrieves responses, and performs validations.

      I'm currently looking for a code coverage tool that can accurately measure the code coverage of my backend code when triggered by the API testing framework. I've tried using Istanbul and NYC with instrumented code, but the results are not as expected.

      Could you please recommend a reliable code coverage tool or suggest an approach to effectively measure the code coverage of my Node.js/Express.js backend code in this setup?

      See more
      Shared insights
      on
      Node.jsNode.jsGraphQLGraphQLMongoDBMongoDB

      I just finished the very first version of my new hobby project: #MovieGeeks. It is a minimalist online movie catalog for you to save the movies you want to see and for rating the movies you already saw. This is just the beginning as I am planning to add more features on the lines of sharing and discovery

      For the #BackEnd I decided to use Node.js , GraphQL and MongoDB:

      1. Node.js has a huge community so it will always be a safe choice in terms of libraries and finding solutions to problems you may have

      2. GraphQL because I needed to improve my skills with it and because I was never comfortable with the usual REST approach. I believe GraphQL is a better option as it feels more natural to write apis, it improves the development velocity, by definition it fixes the over-fetching and under-fetching problem that is so common on REST apis, and on top of that, the community is getting bigger and bigger.

      3. MongoDB was my choice for the database as I already have a lot of experience working on it and because, despite of some bad reputation it has acquired in the last months, I still believe it is a powerful database for at least a very long list of use cases such as the one I needed for my website

      See more
      HTML5 logo

      HTML5

      152.1K
      2.2K
      5th major revision of the core language of the World Wide Web
      152.1K
      2.2K
      PROS OF HTML5
      • 448
        New doctype
      • 389
        Local storage
      • 334
        Canvas
      • 285
        Semantic header and footer
      • 240
        Video element
      • 121
        Geolocation
      • 106
        Form autofocus
      • 100
        Email inputs
      • 85
        Editable content
      • 79
        Application caches
      • 10
        Easy to use
      • 9
        Cleaner Code
      • 5
        Easy
      • 4
        Semantical
      • 4
        Websockets
      • 3
        Audio element
      • 3
        Content focused
      • 3
        Modern
      • 3
        Better
      • 2
        Compatible
      • 2
        Portability
      • 2
        Semantic Header and Footer, Geolocation, New Doctype
      • 2
        Very easy to learning to HTML
      CONS OF HTML5
      • 2
        Easy to forget the tags when you're a begginner
      • 1
        Long and winding code

      related HTML5 posts

      Jan Vlnas
      Senior Software Engineer at Mews · | 26 upvotes · 473K views
      Shared insights
      on
      HTML5HTML5JavaScriptJavaScriptNext.jsNext.js

      Few years ago we were building a Next.js site with a few simple forms. This required handling forms validation and submission, but instead of picking some forms library, we went with plain JavaScript and constraint validation API in HTML5. This shaved off a few KBs of dependencies and gave us full control over the validation behavior and look. I describe this approach, with its pros and cons, in a blog post.

      See more
      Jonathan Pugh
      Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 3.1M views

      I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

      For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

      Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

      I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

      I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

      I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

      I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

      For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

      For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

      For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

      I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

      So that's my latest mobile stack. What tools do you use? Have you tried these ones?

      See more