Protractor VS hyperapp

Cypress is a next-generation front-end Automation testing tool built for modern web applications. It is a JavaScript-based end-to-end testing framework and is known for faster test execution as compared with other testing tools (like Selenium or Protractor).

Protractor repo (link)

Protractor has been deprecated for a while on the Angular CLI side and given Nx has had Cypress support for a while it has never been a popular choice. Starting with this release we're deprecating the generator for setting up Protractor and we're planning on removing support entirely in Nx v15.

In recent releases, the Angular CLI kept reducing its feature set, mainly due to tools such as Protractor as well as TSLint being deprecated. As a result, starting with Angular 14, the Angular CLI provides the following when generating a new application:

The Protractor testing framework was created for e2e testing of Angular apps. https://www.protractortest.org/

Future of Angular E2E & Plans for Protractor · Issue #5502 · angular/protractor

In April, the Angular team has announced plans to end the support of Protractor at the end of 2022.

"The Angular team plans to end development of Protractor at the end of 2022 (in conjunction with Angular v15)." - https://github.com/angular/protractor/issues/5502

Angular will deprecate Protractor soon https://github.com/angular/protractor/issues/5502

Please check out https://github.com/jorgebucaran/hyperapp

The likely reason it never caught on, is that it has similar pitfalls as Backbone:

- manually attaching DOM elements to view controllers

- manually attaching child views

- models which have to be wired individually via .listenTo

- possibility of infinite loops if the events accidentally recurse

A better tiny alternative would be hyperapp[1] or even Preact, that has a similar bundle size.

[1] https://github.com/jorgebucaran/hyperapp

If they're focused on performance and bundle size, it's your chance to try some minimalistic exotic stuff like hyperapp (https://github.com/jorgebucaran/hyperapp) or mithril (https://mithril.js.org/) Just for fun

With a bit of a deadline (due to a mixture of procrastination and confidence that Vue would work) I needed something quick. I have also used Hyperapp in the past but that looks like a dead project right now (although arguably it has all the functionality you need so why keep developing it?).

I’m glad it left that impression! My thoughts have clarified a bit since I read that post, and I think what I describe is more declarative, like React. But the best places to read about it (for web devs) are in Elm!

There is also this new thing I found that seems to really lean into the core of what being functional means here: https://github.com/jorgebucaran/hyperapp

After a while, you see that basically all systems can be modeled as event-driven, functional systems. It’s a flexible model, and fits beautiful into web dev where the semantics are very clear: the system is the web app and events are clicks, keyboard events, asynchronous calls...

Hyperapp is 1kb.

- Hyperapp (https://github.com/jorgebucaran/hyperapp) - Preact - Svelte - React / Vue

I'll tell you what I've learnt from struggling with a bug that made me lose a couple of weeks. The application framework used in this post is Hyperapp, but I guess the same problem can be found in frameworks based on transforming the state of "Single Source of Truth" with pure functions (such as Elm, Redux, so on) if we use them in a wrong way.

Personally, I try my best to avoid bringing in dependencies as much as possible, and try to limit my exposure to only dependencies with low/shallow transitive dependency counts. Unfortunately, this is pretty hard, especially in corporate settings. What we need more of are the opposite of what we've been collectively praising: we need more monolithic packages. Case in point: lodash.template is currently vulnerable with no mitigation, even though lodash itself is not. That's just sloppy publishing practices. Esbuild is a great start over the webpack/babel maze of dependencies. There's a stdlib effort along those lines that hopefully would also help. There's a bunch of micro-frameworks that are used in production just fine and have little to no dependencies.