17 private links
The Transition component lets you describe a transition from one component state to another over time with a simple declarative API. Most commonly it's used to animate the mounting and unmounting of a component, but can also be used to describe in-place transition states as well.
React implements a browser-independent DOM system for performance and cross-browser compatibility. We took the opportunity to clean up a few rough edges in browser DOM implementations.
npm install -g
won't finish installs on WSL Ubuntu. What I did to fix this issue:
- turned of any application running on port 3000
- cleaned npm cache
- some said I should remove package.json.lock, but what about Yarn?
Customizing tmux is as easy as editing a text file. tmux uses a file called tmux.conf to store its configuration. If you store that file as `~/.tmux.conf
(Note: there’s a period as the first character in the file name. It’s a hidden file) tmux will pick this configuration file for your current user. If you want to share a configuration for multiple users (e.g. if you should feel the urge to start tmux as super user (please think about this carefully!)) you can also put your tmux.conf into a system-wide directory. The location of this directory will be different accross different operating systems. The man page (man tmux) will tell you the exact location, just have a look at documentation for the -f
parameter.
Extension for Visual Studio Code - Sublime Text's babel-sublime grammar in VS Code.
To kill a panel, use Ctrl + key
x
Shoelace.css is a lightweight, forward-thinking CSS library built with future CSS syntax. It’s easy to use and highly customizable. Bootstrap users will find it familiar, yet refreshing.
You can use Shoelace with just about any browser. The CDN version is great for prototyping, but to take advantage of all its features you should build Shoelace from source.
mintty-colors
is a python package that is easiest to install using pip.
pip install mintty-colors
This installs a command-line tool - mtc that let's you control the colors of your mintty session.
I find as I am building my redux app, one piece of functionality at a time, I keep needing to add {actionTypes, actions, reducer} tuples for each use case. I have been keeping these in separate files and even separate folders, however 95% of the time, it's only one reducer/actions pair that ever needs their associated actions.
To me, it makes more sense for these pieces to be bundled together in an isolated module that is self contained, and can even be packaged easily into a library.
Block Element Modifier is a methodology that helps you to create reusable components and code sharing in front-end development
Easy
To use BEM, you only need to employ BEM’s naming convention.
Modular
Independent blocks and CSS selectors make your code reusable and modular.
Flexible
Using BEM, methodologies and tools can be recomposed and configured the way you like.
// main.scss
.pony {
@import 'sub';
font-size: 100px;
}
// _sub.scss
.chow {
color: tomato;
}
Will compile to:
.pony { font-size: 100px; }
.pony .chow { color: tomato; }
npm install legally -g # Make it work everywhere
legally # Check licenses of current directory
legally express # Check an npm library's licenses
an open source pastebin with runnable snippets and API. Start coding in your favorite language.
Starter kit for Toucan Toco's components
One of the biggest obstacles for adoption of Angular in the enterprise is technical, but not of the nature that one could expect.
It's hard to convince our boss to use Angular in our next project if we can't even install it in our own PC ;-) ! We would probably want to do an early demo or prototype to get things started.
But many companies have corporate proxies and security policies that make tools like npm hard to try out for the first time.
One of the biggest features of AngularJs is that it does not come necessarily with all the tooling ecosystem, and can be used via simple script tags. Angular 2 and beyond in principle can also, but we really want to use it together with Typescript, the Angular CLI, Webpack and all the tooling ecosystem.
These notes summarize some of my discoveries (re-)learning GNU Emacs. Since these are my personal notes, it may help to briefly describe my background. I used Emacs on Unix from somewhere around 1990 until 1995. Then in 1995 I began using Windows as my primary operating system and stopped using Emacs. In 2010 I decided to give Emacs on Windows another try. I may not mention some basic things just because I remember them from my initial experience.