Viraj G. Kulkarni (विराज गु. कुलकर्णी) virajkulkarni14

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

A collapsible section with markdown

Click to expand!

Heading

A numbered
list
- With some
- Sub bullets

This is an incomplete, ever-changing curated list of content to assist people into the worlds of Data Science and Machine Learning. If you have a recommendation for something to add, please let me know. If something isn't here, it doesn't mean I don't recommend it, I just may not have had a chance to review it yet or not.

I will generally list things in order of easier to more formal/challenging content.

It may feel like there is an overwhelming amount of stuff for you to learn (because there is). But, there is a guided path that will get you there in time. You need to focus on Linear Algebra, Calculus, Statistics and probably Python (or R). Your best bet is to get a Safari Books Online account (https://www.safaribooksonline.com) which you may already have access to through school or work. If not, it is a reasonable way to get access to a tremendous number of books and videos.

I'm not saying you will get what you need out of everything here, but I have read/watched at least some of all of the following an

	import React from "react";
	import PropTypes from "prop-types";

	const UserCard = ({ user }) => {
	return (
	<ul>
	<li>{user.name}</li>
	<li>{user.age}</li>
	<li>{user.email}</li>
	</ul>

	<body>
	<div id="⚛️"></div>
	<script src="https://unpkg.com/react@16.0.0/umd/react.development.js"></script>
	<script src="https://unpkg.com/react-dom@16.0.0/umd/react-dom.development.js"></script>
	<script src="https://unpkg.com/babel-standalone@6.26.0/babel.js"></script>
	<script type="text/babel">
	ReactDOM.render(<div>Hello World!</div>, document.getElementById('⚛️'))
	</script>
	</body>

	#!/bin/sh

	###
	# SOME COMMANDS WILL NOT WORK ON macOS (Sierra or newer)
	# For Sierra or newer, see https://github.com/mathiasbynens/dotfiles/blob/master/.macos
	###

	# Alot of these configs have been taken from the various places
	# on the web, most from here
	# https://github.com/mathiasbynens/dotfiles/blob/5b3c8418ed42d93af2e647dc9d122f25cc034871/.osx

	// A Declarative Pipeline is defined within a 'pipeline' block.
	pipeline {

	// agent defines where the pipeline will run.
	agent {
	// This also could have been 'agent any' - that has the same meaning.
	label ""
	// Other possible built-in agent types are 'agent none', for not running the
	// top-level on any agent (which results in you needing to specify agents on
	// each stage and do explicit checkouts of scm in those stages), 'docker',

	#!/bin/bash
	#
	# Open new Terminal tabs from the command line
	#
	# Author: Justin Hileman (http://justinhileman.com)
	#
	# Installation:
	# Add the following function to your `.bashrc` or `.bash_profile`,
	# or save it somewhere (e.g. `~/.tab.bash`) and source it in `.bashrc`
	#

	# to generate your dhparam.pem file, run in the terminal
	openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048