SSH remote port forward
Easy test setup without side effects
Convert Windows backslash paths to slash paths
Provides "ui" for testing frameworks such as mocha/jasmine which allows to define lazy variables and subjects
Find the position of grapheme cluster breaks in a string
SSH2 client and server modules written in pure JavaScript for node.js
Jest plugins to emulate RSpec syntax and structure.
Shared types and schemas for Forward MPC Client
WebSocket client for Forward MPC operations
A node fluent protocol compatible logger
Parses forwarded emails and extract content
Utility for filtering Styled System props with Emotion's shouldForwardProp option
An inline CSS processor to translate CSS properties to React Native styles.
Flexible, lightweight transport layer for GraphQL
AWS SDK for JavaScript Route53resolver Client for Node.js, Browser and React Native
Undertaker custom registry supporting forward referenced tasks.
TypeScript definitions for @styled-system/should-forward-prop
Forward events from any Node EventEmitter to another EventEmitter.
Adds context as an alternative to describe to jest.
Webpack loader that enables glob patterns in ES6 imports.
A wrapper around React.forwardRef() that allows HTML attributes and prop types to be derived from the as prop.
Regular expression matching for URL's. Maintained, safe, and browser-friendly version of url-regex. Resolves CVE-2020-7661. Works in Node v10.12.0+ and browsers.
Parses forwarded emails and extract content
Adds a Given-When-Then DSL to jasmine as an alternative style for specs
Set of RSpec matchers for checking class method to instance method forwarding.
A plugin to RSpec and YARD that allows you to define illustrative objects in your examples that will be forwarded to the output formatter. The results can be imported into YARD, which makes your generated specs and documentation more readable, illustrative, and explanatory.
Spectie (rhymes with "necktie") is a pure Ruby acceptance testing framework for RSpec. The philosophy of Spectie is that, since the business stakeholders on most projects don't care about exactly how you test, you're free to write the acceptance tests on a project how *you*, the developer, need to in order to ensure that the implementation is correct, easily understood, and maintainable. Furthermore, since you're a developer, the easiest, most straight-forward and maintainable way for you to write your tests is by using the highly expressive language that you're already coding in for the project; that's Ruby, baby!