alexdiliberto

import Ember from 'ember';

export default Ember.LinkComponent.extend({
  tagName: 'div',
  classNames: ['test-link-to-component']
});

alexdiliberto

        defeatureify: {
            'enableStripDebug': true,
            'debugStatements': [
                'Ember.default.warn',
                'Ember.default.assert',
                'Ember.default.deprecate',
                'Ember.default.debug',
                'Ember.default.Logger.assert',
                'Ember.default.Logger.debug',
                'Ember.default.Logger.error',

alexdiliberto

/* 
  matches the last item only if the list has exactly N items
  e.g. for N = 3:
*/

$N: 3;

:nth-last-child(-n+#{$N}):first-child ~ li:nth-child(#{$N}) {
  color: red;
}

alexdiliberto

import Ember from 'ember';

export default Ember.Component.extend({
});

alexdiliberto

#!/bin/bash
echo "Generating an SSL private key to sign your certificate..."
openssl genrsa -des3 -out myssl.key 1024

echo "Generating a Certificate Signing Request..."
openssl req -new -key myssl.key -out myssl.csr

echo "Removing passphrase from key (for nginx)..."
cp myssl.key myssl.key.org
openssl rsa -in myssl.key.org -out myssl.key

alexdiliberto

You can use async/await in your Ember testing suite, today! This blog post explains the situation pretty thoroughly.

There are three ways we can get it to work. If you try it without any changes, you will get the error regeneratorRuntime is not defined.

Largest

One way to get around this is to enable every polyfill - but that's pretty big to include in your production application code unnecessarily (30kb minified & gzipped).

This also lets you use async/await in your app code.

Medium

alexdiliberto

If you have a package where a lot of people are still using a legacy version of it you might want to keep pushing (security-)fixes to that "branch".

Let's say the "latest" version of your package is "5.4.0", but there is as significant amount of people still using "4.7.4" – the last version you released before doing "5.0.0".

You found a critical bug in "5.4.0" and push it as out as "5.4.1", but it applies to "4.7.4" as well and so you want to do "4.7.5".

Assuming you have semantic-release already set up, you can follow these steps to get that "4.7.5" legacy support release out.

1. Go to the relevant commit: git checkout v4.7.4
2. Create a new branch from it: git checkout -b 4.x (You can choose any branch name, just make sure to use the same in step 3)

alexdiliberto

import Ember from 'ember';
import Changeset from 'ember-changeset';
import lookupValidator from 'ember-changeset-validations';

export default Ember.Component.extend({
  init() {
    this._super(...arguments);
    
    let user = Ember.get(this, 'user');
    let validations = Ember.get(this, 'validations');

alexdiliberto

/* eslint-env node */
'use strict';

const EmberApp = require('ember-cli/lib/broccoli/ember-app');

module.exports = function(defaults) {
  let env = EmberApp.env();
  let plugins = [];

  if (env === 'production') {

alexdiliberto

{
  "name": "my-lerna-project",
  "private": true,
  "devDependencies": {
    "bower": "^1.8.0",
    "lerna": "^2.0.0",
    "lerna-wizard": "^1.0.9",
    "rimraf": "^2.6.1"
  },
  "scripts": {