You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this document I am using Sass's SCSS syntax. You can choose to use the indented syntax
in sass, if you prefer it, it has no functional differences from the SCSS syntax.
For Less, I'm using the JavaScript version because this is what they suggest on the website.
The ruby version may be different.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Example of using composer.phar for wordpress plugins/themes dependency management
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(Hi, I'm Adam Smith. I started Xobni in 2006, which has written the most sophisticated and successful MS Outlook addin in history. This took millions of dollars and several years of work by some of the best programmers in the valley. Other startups have thrown millions of dollars at building Outlook addins and failed. This is my take on the idea of building a new MS Outlook addin as of 2012.)
My general advice is avoid any Outlook addins or desktop software if at all possible. More and more stuff is moving to the web, and the table stakes of doing anything reasonably well in Outlook are remarkably high. Consider it to be on the same level of making hardware with regards to the cost of bugs/mistakes, amount of black art, etc., but maybe a little higher since there's a much weaker ecosystem of people doing it. I pasted below in this email an old list of "gotchas" or things-to-know I made after leaving Xobni. It's not comprehensive but will include some of the biggest ones from a pain perspective.
`module.exports =` and ES6 Module Interop in Node.js
module.exports = and ES6 Module Interop in Node.js
The question: how can we use ES6 modules in Node.js, where modules-as-functions is very common? That is, given a future in which V8 supports ES6 modules:
How can authors of function-modules convert to ES6 export syntax, without breaking consumers that do require("function-module")()?
How can consumers of function-modules use ES6 import syntax, while not demanding that the module author rewrites his code to ES6 export?
@wycats showed me a solution. It involves hooking into the loader API to do some rewriting, and using a distinguished name for the single export.
This is me eating crow for lots of false statements I've made all over Twitter today. Here it goes.