$ ssh [email protected] -A
Ref: http://man.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/ssh.1
$ ssh [email protected] -A
Ref: http://man.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/ssh.1
When you want to include i18n
in your react component library, but the two use cases of i18next
conflict with one another — long story short, you need I18nextProvider
.
Error message looks like this:
var api = require("!./node_modules/[email protected]@style-loader/dist/runtime/injectStylesIntoStyleTag.js");
If you’re using Storybook, or multiple webpack configs of dev/prod, or simply multiple rules… Either way, this error means you’ve specified rules for CSS more than once.
For example, Storybook already has a set of default rules for various file types, and CSS is one of them, so you cannot specify custom CSS
rules again.
I know, it’s not the most helpful error message in the world. Here’s a translation. If you get this error, it’s one of three things:
REGION
in environment variablesREGION
Sometimes we just need to explicitly set prettier config path in vscode:
"prettier.configPath": ".prettierrc"
Every few weeks where I don’t touch Docker I tend to forget the basics:
Continue readingProvided we have /styles
under root, add the following resolve in your webpack config:
Use browser
field in package.json
:
"browser": {
...
"package-name": false
}
First I tried the normal ways, like using html-to-react and the alike, but somehow due to some finicky formatting of strings, this library just flat out refuses to convert legitimate HTML. On top of that, NextJS was complaining loudly about Prop dangerouslySetInnerHTML did not match
.
Time to bring out the big guns.
Continue readingHow a simple config as such could be so hidden: