element-ui runtime es component - el-button
Node.js final http responder
Execute a callback when a request closes, finishes, or errors
Execute a listener when a response is about to write headers
Encode a URL to a percent-encoded form, excluding already-encoded sequences
response extensions for tinyhttp
Evaluate node require() module content directly
Fake HTTP injection library
A PAC file proxy `http.Agent` implementation for HTTP
An HTTP(s) proxy `http.Agent` implementation for HTTP
Simple middleware-style router
React package for working with the DOM.
An HTTP(s) proxy `http.Agent` implementation for HTTPS
node-httpreq is a node.js library to do HTTP(S) requests the easy way
Nodejs http response builder
A response helper that detects & handles Content-Types
Fast, unopinionated, minimalist web framework
Node's domain module for the web browser. This is merely an evented try...catch with the same API as node, nothing more.
FaaS (Function as a service) framework for writing portable Node.js functions
A SOCKS proxy `http.Agent` implementation for HTTP and HTTPS
Lightweight debugging utility for Node.js and the browser
Mocks node.js http.ServerResponse. See also `mock-req`.
<!-- automd:badges color=yellow -->
Retrying made simple, easy and async
A Facebook Share button for convenient re-usage
Prevent form re-submition when hitting 'back'. Instead, choose where to redirect the user if she hits 'back', e.g. to the edit page of the record that was created.
Prevent users sending duplicate requests by rapidly clicking links and buttons.
Remember the route prior to the current controller and redirect/use later In rails project, one common case is one form used to create or update an object can be routed from more than one page, when the object is created or updated, it should be redirected back to wherever it came from. Rails redirect_back doesn't work in this case because: 1. redirect_back in create/update action will go back to new/edit form. 2. usually the form is re-rendered if any error exists, which basically breaks the redirect_back. rails-source-path can hanlde this by explicily specifying the entry actions and remember the previous route in session store, hence can be used in the whole controller. Also a helper method is providered so it can be used in view like 'back' or 'cancel' button.
QA Robusta is an automation framework easing pain points away from automation test case writers. How is pain relieved? * Elements, such as links, buttons, and other html objects are defined in one location. This ensures over time the user won't have definitions spread out throughout different layers of code requiring time consuming updates if the application under test is modified. * Well defined flows allows the user to have a common means for navigating and controlling interactions with the application under test. This takes all logic out of test classes and yields in higher more modular code re-use. * When an application requiring testing has the elements and flows implemented less code savy resources can easily add new test cases once trained on how to access the flows and elements. * When ever a link or button is clicked a screen shot is taken * Results are available under site/results directory in html format. Report includes the rdoc on a per test class method along with any screen shots taken. Example report: https://cyberconnect.biz/opensource/demo_results.html * Transparent remote Unix command execution leading to well defined interfaces for common task. For example, one may have a class defined specifically for RemoteUnixNetwork. This class would have methods such as, assign_ip, ifup, ifdown, etc. This class then would be able to perform these task on any remote Unix machine. * Executes the same on Windows or Linux/Unix environments. Developers have the freedom to develop on the platform of choice. * Mechanize extension: Allows the user to define a web application's page elements in a YAML format and provide navigation paths accessing the YAML structure to interact with the web application. Users can also perform direct http.post or any other mechanize functionality when defining state-full interfaces to hit a web application without going through a browser.