Explore >> Select a destination
|
You are here 
|
steakenthusiast.github.io | ||
| | | | |
backlight.dev
|
|
| | | | | Ensuring a consistent experience when developing a common library or Design System as a team could quickly become a high-challenge. Here are our advices on how to use Eslint to enforce this experience's consistency. | |
| | | | |
ariya.io
|
|
| | | | | A common approach to analyze JavaScript source statically is to parse the source into an abstract syntax tree (AST) and then to traverse the AST. An alternative approach that might work in a few cases is to inspect each syntax node as it is constructed. | |
| | | | |
krasimirtsonev.com
|
|
| | | | | Replacing code for production with Babel transformation / If you are building some sort of an app, Babel is probably part of your build system. It is that thing which converts our fancy code to valid, working in a browser, JavaScript. Just recently at work I had to design a solution that swaps a class based on the environment. Or in another words, we have logic that should not reach our users. The file should be available locally and on our staging environment but not in production. A tiny Babel plugin was the cheapest solution for me so I decided to share the result. | |
| | | | |
www.s-anand.net
|
|
| | | In 1994, I learnt Perl. It was fantastic. I used it to: In 2006, I was convinced I should stick to Perl over Python. In 2008, Google launched AppEngine and it provided free hosting (which was a big deal!) but had only 2 runtimes: Java and Python. The choice was clear. I'd rather learn Python ... Perl, 1994-2011 Read More » | ||
