Note: this article will not make much sense unless you know the basics of GraphQL, an awesome technology we use at Slite. We recommend you get a brief understanding of it before going forward. Here are some resources.
What are n+1 requests?
n+1 requests are the most obvious optimisation issue one might encounter when…
If you’re using react, chances are that you are using the whole babel + jsx + webpack stack (and you’re goddamn’ right).
Your components files, the 1627219 of them, look like:
import React from 'react'export function YourComponent() {
return <span>Hello, I do nothing</span>
}
Now here is the protip that will save a lot of time, in your webpack.config.js:
plugins: [
new webpack.ProvidePlugin({
React: 'react',
}),
],This lets you omit the import React from ‘react’ line in all of your component files and this will work just as well:
export function YourComponent() {
return <span>Hello, I do nothing</span>
}Bonus: As you don’t import React directly anymore, this prevents eslint from bugging you with `’React’ is defined but never used no-unused-vars`.
TL;DR:
This article explains how to make your unit test setup and workflow as simple as possible (assuming you use babel).
- code and tests just next to each other in the same file
- tests run in the browser every time you build your app, just like regular code
- wipe tests…
Rationale
EDIT: I just released rm_local_modules, a really simple module best used as a npm preinstall script so you can quickly update (delete + reinstall) all your local modules simply. Problem is, npm 3 preinstall is broken.
Most large javascript application built using npm modules have the same problem: tons of…
