
Security News
Risky Biz Podcast: Making Reachability Analysis Work in Real-World Codebases
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
@wealthsimple/patchwork
Advanced tools
Patchwork is Wealthsimple's UI Component library for React applications.
It aims to provide a first class DSL for building user interfaces that can:
Are you a developer trying to use patchwork to implement features in your application? Check out the Users' Guide.
Are you a designer or a developer adding features to patchwork itself? Check out the Implementers' Guide.
Wonder why something is implemented a certain way? Curious about the reasoning behind this code-base's conventions?
Decisions of this nature are recorded in this repo as Architectural Decision Records (ADRs).
You can consume this project one of two ways:
For compatibility with our internal toolchain, I just expose the ES6+Flow source code for now.
That means you'll need a compatible babel config + bundler setup in your project. Check this project's
.babel.config.js
for the specific configuration.
Then import things from @wealthsimple/patchwork
to use them:
import { Box } from '@wealthsimple/patchwork';
Not running a transpiler? Running a transpiler that's not Babel (e.g. TypeScript)? Not using Flow?
No problem. We also expose a UMD-ified ES5 version of this library in the dist
folder:
ES6/TypeScript:
import { Box } from '@wealthsimple/patchwork/dist';
CommonJS:
const { Box } = require('@wealthsimple/patchwork/dist');
To run patchwork locally run ( on port 9001):
yarn storybook
If using a compatible IDE ( RubyMine ) you can display flow errors by linking the flow library:
As of January 2021, Wealthsimple is legally required to make any of our websites WCAG 2.0 Level AA compliant. Accessibility is sometimes forgotten about when developing fast features in web, but it’s extremely important in providing all of our clients the same, equal-level of access to our services. Patchwork must be accessible because it serves as the building blocks for our entire application.
In order to test accessibility, we have some scanning jobs in CI that will flag things like missing screenreader labels, insufficient text/background colour contrasts.
Note: Automated testing can't catch everything. When you make changes or create a new component, before you launch it to the public you should run it by the Web a11y testing guidelines.
FAQs
Wealthsimple's React Styleguide and Component Library
The npm package @wealthsimple/patchwork receives a total of 269 weekly downloads. As such, @wealthsimple/patchwork popularity was classified as not popular.
We found that @wealthsimple/patchwork demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 11 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
Security News
/Research
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.
Security News
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.