rafakato

'use strict';

const internals = {};

exports.errors = {
    root: 'value',
    key: '"{{!key}}" ',
    messages: {
        wrapArrays: true
    },

dchowitz

Debugging ES6 in VS Code

My current editor of choice for all things related to Javascript and Node is VS Code, which I highly recommend. The other day I needed to hunt down a bug in one of my tests written in ES6, which at time of writing is not fully supported in Node. Shortly after, I found myself down the rabbit hole of debugging in VS Code and realized this isn't as straightforward as I thought initially. This short post summarizes the steps I took to make debugging ES6 in VS Code frictionless.

What doesn't work

My first approach was a launch configuration in launch.json mimicking tape -r babel-register ./path/to/testfile.js with babel configured to create inline sourcemaps in my package.json. The debugging started but breakpoints and stepping through the code in VS Code were a complete mess. Apparently, ad-hoc transpilation via babel-require-hook and inline sourcemaps do not work in VS Code. The same result for attaching (instead of launch) to `babel-node

raymyers

angular.module('myapp.directive.blacklist', []).
directive('maBlacklist', [
  function() {
    return {
      restrict: 'A',
      require: 'ngModel',
      scope: {'blacklist':'=gsBlacklist'},
      link: function($scope, $elem, $attrs, modelCtrl) {

        var check = function(value) {

jmar777

First, we need to figure out what the actual error is.  This is obviously frustrating given that the error message is intentionally truncating it.

1) SSH in to your node (various guides available for this if you're not already familiar with this).
2) Run this command (basically an Elastic Beanstalk wrapper command for npm install I found in a blog post [1]):
   $ sudo /opt/elasticbeanstalk/containerfiles/ebnode.py --action npm-install 2
3) Find the actual error message in the output from the npm install.

Once you know the error, it should hopefully be fairly obvious how to fix it.  I've run into two different errors over the last couple days on Elastic Beanstalk:

The first was a dependency that was using the new "^X.Y.Z" version syntax, which is only supported in Node >= v0.10.26 (whereas Elastic Beanstalk only supports up to v0.10.21 as of today).  The solution here was easy: hardcode a dependency version *prior* to when that dependency adopted to the new syntax.

there4

class package_dev_tools
{

  package
  {
    'git-core':
      ensure  => present
  }