Andrey Sidorov sidorares

## readme.md

      
              1 file
            
          
              0 forks
            
          
              2 comments
            
          
              9 stars
            
          
                max-mapper
                / readme.md
            
            
              Last active
              October 30, 2015 03:05
            
              
                node.js release questions
              
          
    As a maintainer of native node add-on modules I have some questions about when and why NODE_MODULE_VERSION changes:
(@rvagg has anwered these in the comments below)

does v8 use semver? how do you know when a v8 version breaks ABI compatibilility?
is there a semantic meaning for v8 version numbers or is it arbitrary?
who maintains this google doc I found? is it official?
why is the latest entry from may in the v8 changelog? https://chromium.googlesource.com/v8/v8.git/+/master/ChangeLog
how can you tell when all these future v8 versions will be stable? https://chromium.googlesource.com/v8/v8.git/+refs
why must a node major version correspond to a specific v8 version? e.g. node v5 uses v8 4.6 and won't upgrade to 4.7


## await-babel-repl.js
const repl = require('repl');
const babel = require('babel-core');

function preprocess(input) {
  const awaitMatcher = /^(?:\s*(?:(?:let|var|const)\s)?\s*([^=]+)=\s*|^\s*)(await\s[\s\S]*)/;
  const asyncWrapper = (code, binder) => {
    let assign = binder ? `global.${binder} = ` : '';
    return `(function(){ async function _wrap() { return ${assign}${code} } return _wrap();})()`;
  };
	const repl = require('repl');
	const babel = require('babel-core');

	function preprocess(input) {
	const awaitMatcher = /^(?:\s(?:(?:let\|var\|const)\s)?\s([^=]+)=\s\|^\s)(await\s[\s\S]*)/;
	const asyncWrapper = (code, binder) => {
	let assign = binder ? `global.${binder} = ` : '';
	return `(function(){ async function _wrap() { return ${assign}${code} } return _wrap();})()`;
	};