Electrode.io like Meteor from WalmartLabs?

#1

This is interesting project like MeteorJS, have anyone tried? I didn’t see any discussion here.

http://www.electrode.io/

3 Likes
:satellite: TRANSMISSION #16: Help pick topics
#2

Electrode’s testing framework uses Nightwatch, so some of us working with Clinical Meteor have been tracking it. Specifically, the first device driver for TestArmada is something called Magellan-Nightwatch.

So their testing tools, at the very least, will be compatible with anybody using Meteor/Nightwatch; meaning there will be clear refactor paths and migration routes between the two frameworks (including Clinical Meteor). Plus, they use React. So there will be a lot of fluidity between Meteor projects and Electrode projects, I suspect.

1 Like
#3

Yeah it looks really cool, excited to see where it goes!

#4

I’m blown away by Electrode! I didn’t want to like it because it’s WalMart, but they have made great choices! (React, Webpack, Mocha, enzyme, etc etc)

Above the fold SSR!

Bundle analyzer to figure out where KB size is coming from in production bundles:
http://www.electrode.io/docs/bundle-analyzer.html

A React module explorer of prebuild components with documentation: http://www.electrode.io/docs/electrode_explorer.html

This is impressive. I hope Meteor’s newfound focus on curating the best of JS world and helping developers avoid JS fatigue means we see some of these modules appearing in Meteor docs as recommended tools! Would love to keep coming back to Meteor as the go-to source for what is best to use.

1 Like
#5

I think this is going to be a great choice for optimizing server side rendering with Apollo or ddp! It’s focused on a lot of things meteor isn’t, like really fast initial load time. Meteor is optimized more for an application like experience where the initial load tims isn’t as critical, so I think they can be good complements to each other.

1 Like
#6

I doesn’t know about Nightwatch. Taking a look I saw that the package has an red flag on atmosphere. Problems? https://atmospherejs.com/clinical/nightwatch

#7

The flagged Atmosphere package relies on the now-defunct Velocity project. Use the NPM package instead.

#8

Thanks, I’ll check it out

#9

Agreed, I haven’t seen Android and iOS app deployment with electrode.io (maybe I missed it, but doubt it). The tight integration with Cordova is a big plus as we can deploy rather quickly our apps on the app stores (not to mention all the plugins available, such as ios-rtc and in-app purchase).

#10

Looks promising.

Did anyone find a decent review or blog post about it (except the official ones)?

E.g. a comparison to Meteor

#11

It’s not clear to me if this is just an opinionated combination of tools/libraries or if it adds something new?

1 Like
#12

They spent a lot of time getting server side rendering and testing parallelization working at a scale few others using.

1 Like
#13

@sashko do you think MDG core team could provide an example simple application of electrode + apollo?

Would be nice to share the same port and avoid cross domain scripting limitations. For example URLs would be:

http://server:port/myapp
http://server:port/myapp/apollo

For above URL structure is there a problem that electrode uses Hapi.js web server? (not express)

#14

No problem - Apollo server works with Hapi already! I don’t know enough about it to build an app right now but if someone wants to do it I’d be glad to help!

#15

Sometime next week we can start a small sample application that combines electrode with Apollo. @sashko thanks for offer to help; probably we will need some guidance for best practice and review.

1 Like
#16

Any update on this? Looking forward to seeing the result.

#17

I guess electrode never really took off?

#18

Really? But still contributing. The whole idea over Electrode-native is very challenging although there are too many beneficial on this to have something like electrode-native feature in an org sized mobile app. For example having multiple individual teams working on different features on App and they can work on their app without any intervention from other teams.