This is an idea i had for a blog series. It is sort of a reference for me since there are some modules that i am not to familiar with.

This also goes along with the talk i submitted for Empirenode about "The node core modules less traveled"

i'm basically going to go straight down the list on the docs page:

https://nodejs.org/dist/latest-v6.x/docs/api/

Current Post

Assert - http://blog.lholmquist.org/node-core-modules-exploration/
Buffers - http://blog.lholmquist.org/node-core-modules-exploration-buffers/

• Conference website: http://empirenode.org/
• Dates: November 7, 2016
• Submission Link: https://docs.google.com/forms/d/e/1FAIpQLSf6tyFQAxQB0FQG9tEe2xOtQ_fJPSf_jU0J6QglTfWYPzlnIQ/viewform?c=0&w=1
• Accepted: Unknown

Tracing Asynchronous Operations with Node's AsyncWrap API

This is not the exact title and description, because I submitted through a Google
form and didn't save a copy of what I wrote. 👎

Tracing asynchronous code paths in Node.js is notoriously difficult, making
it very hard to understand what is going wrong when your application blows up.
Since Node.js version 4.0, however, Node has included an as-yet undocumented,
and still in progress feature known as AsyncWrap. In this talk you will learn
about the upcoming AsyncWrap API and how you can use it to to gain a better
understanding of what went wrong when your application fails, and where
potential asynchronous processing bottlenecks are lurking.

Additional Notes

I will be presenting the AsyncWrap API in an overview format, with some
discussion of the potential usages of the API in user applications and
custom frameworks. I will review some existing packages that provide an
abstraction layer over this low-level API, learn where unexpected gotchas
lay in wait, and finally demonstrate the development of a simple package,
making use of the new AsyncWrap API.

Speaker

Lance Ball (@lanceball), Senior Software Engineer, Red Hat, Inc.

http://lanceball.com

Lance Ball is a part of the JBoss division of Red Hat, working on a team
known as project:odd. Lance and his cohorts are tasked with researching and
prototyping new software which may or may not ever see the light of day.
He is an active open source contributor, an author of several NPM modules,
and a Core committer for the Node.js project. In addition to Node.js, you'll
find his contributions in many other well-known open source projects
including Wildfly Swarm, Vert.x, DynJS, and Torquebox.

Previous Speaking Engagements

• Microservices in a Java EE World - Red Hat Microservices Architecture Day 2015
• Process Bindings: How to do Node.js on the JVM - CodeMash 2015
• Vert.x: Async Data From Cluster to Browser - DataIO 2013
• Vert.x - Bringing the Browser to the Cluster - DevIgnition 2013
• Complex Made Simple: Sleep Better with TorqueBox - RailsConf 2012
• Simple Scalability With TorqueBox - Ruby Hoedown 2012
• DataMapper on Infinispan: Clustered NoSQL - StrangeLoop 2012

The entente node.js coding guidelines document has a solid outline but needs to be flushed out. We should think about if this document is meant for bucharest-gold, or a general node.js coding guidelines for Red Hat and/or other interested projects.

https://github.com/bucharest-gold/entente/blob/master/GUIDELINES.md

My original suggestion was to use $USER, but that wasn't ideal because it's just the username on your local machine which may not match your github username.

Then @helio-frota suggested using git config user.name which is a good start, but also not ideal for the same reason, and also because in most git documentation, the user.name configuration value is a full name, like "Lance Ball".

• Write the steps to run benchmarks in our node modules.
• Write the steps to run profile and see the results on chrome dev tools.

Similiar to the connect/express middleware, but for the Hapi framwork.

Hapi calls middleware Plugins

https://github.com/bucharest-gold/szero/milestone/4

Around documentation updates

• Conference website: http://nodevember.org/
• Dates: November 20-21, 2016
• Submission Link: https://www.papercall.io/nodevember2016
• Accepted: Unknown

Tracing Asynchronous Operations with Node's AsyncWrap API

Tracing asynchronous code paths in Node.js is notoriously difficult, making
it very hard to understand what is going wrong when your application blows up.
Since Node.js version 4.0, however, Node has included an as-yet undocumented,
and still in progress feature known as AsyncWrap. In this talk you will learn
about the upcoming AsyncWrap API and how you can use it to to gain a better
understanding of what went wrong when your application fails, and where
potential asynchronous processing bottlenecks are lurking.

Additional Notes

I will be presenting the AsyncWrap API in an overview format, with some
discussion of the potential usages of the API in user applications and
custom frameworks. I will review some existing packages that provide an
abstraction layer over this low-level API, learn where unexpected gotchas
lay in wait, and finally demonstrate the development of a simple package,
making use of the new AsyncWrap API.

Speaker

Lance Ball (@lanceball), Senior Software Engineer, Red Hat, Inc.

http://lanceball.com

Lance Ball is a part of the JBoss division of Red Hat, working on a team
known as project:odd. Lance and his cohorts are tasked with researching and
prototyping new software which may or may not ever see the light of day.
He is an active open source contributor, an author of several NPM modules,
and a Core committer for the Node.js project. In addition to Node.js, you'll
find his contributions in many other well-known open source projects
including Wildfly Swarm, Vert.x, DynJS, and Torquebox.

Previous Speaking Engagements

• Microservices in a Java EE World - Red Hat Microservices Architecture Day 2015
• Process Bindings: How to do Node.js on the JVM - CodeMash 2015
• Vert.x: Async Data From Cluster to Browser - DataIO 2013
• Vert.x - Bringing the Browser to the Cluster - DevIgnition 2013
• Complex Made Simple: Sleep Better with TorqueBox - RailsConf 2012
• Simple Scalability With TorqueBox - Ruby Hoedown 2012
• DataMapper on Infinispan: Clustered NoSQL - StrangeLoop 2012

The package is here. https://www.npmjs.com/package/jvm-npm
The repo is here. https://github.com/nodyn/jvm-npm

It has only ever been released once, but there are people using it. Let's make it live up to the bucharest-standards, eh?

After applying at a minimum the following items from our guidelines doc, we should publish a new release.

• Continuous integration with Travis-CI
• package.json files property
• Code-style/linting

This is a bit of a strange case, because it's meant to run on a JVM Javascript runtime - e.g. nashorn, rhino and dynjs. So with the exception of npm publish the build is actually maven.

This will do a recursive lint into node_modules.

Our current plan on this issue is to write test cases to get results based on:
1. Our doubts and project needs
2. Try to cover affirmations like 'Don't do X, don't do Y'
example: "Don't use prototypes because this has a bad performance"

The repository for the tests: https://github.com/bucharest-gold/perf-quest

So we can add resources (links, videos, etc) on comments here to catch and solve the item 2. ^

• Finish the data mapping between lightbright and hawkular-apm json.
• Avoid trace data polution on hawkular-apm-server from roi module.

Lightbright milestone

https://github.com/bucharest-gold/lightbright/milestone/1

Dependencies

• Info about the Hawkular fragments attributes
• Fill Hawkular-APM with Lightbright traces

Eslint is a more full featured tool than semistandard. We could get semstandard style enforcement using plugins on eslint. Let's figure out the best way to do this.

We have a tool that breaks the build when unused dependencies are found.
So is interesting to add this on the projects.

Ref: https://github.com/hal/dmr.js
Ref: http://hpehl.info/independent-jboss-admin-console.html

• Conference website: http://empirenode.org/
• Dates: November 7, 2016
• Submission Link: http://goo.gl/forms/3rbvdl75Ry6Mu6yk1
• Accepted: Unknown

Node Core Modules Less Traveled

The basic concept of the talk is taking a look at some of the lesser known "Core" modules. Everyone knows what the http module does, but what is the zlib module or punycode?

note: couldn't find the abstract i wrote

Additional Notes

Speaker

Lucas Holmquist (@Sienaluke) Senior Software Engineer, Red Hat, Inc.

lholmquist.org

Previous Speaking Engagements

JUDCon 2013 - Apache Cordova Talk
JUDCon 2013 - Push Talk
Mobile Week 2014 - UnifiedPush Server
jQuery Conf Chicago 2014 - Chromecast: Beyond Streaming Media
Devnation 2015 - Push the future with Webpush, the IoT, embedded, & industry standards

Based on:
bucharest-gold/fidelity#13

Gordon Sim has asked if we could provide him any feedback/comments on https://github.com/grs/rhea the AMPQ node library he's developed.

Milestone

https://github.com/bucharest-gold/fidelity/milestone/3

Dependencies

None known. This is just an enhancement of fidelity to provide a browser version. Should be pretty straightforward.

The levee packages implements the circuit breaker pattern in Javascript. It's written by the people at PayPal. https://github.com/krakenjs/levee

Ella

Just working in this Node.js native plugin done in C++11 that allows you to load and run Java classes in Javascript, enabling you for example to use Java libraries (PDFBox, Lucene, etc..) in your Node.js code.

Features

• You can create Java classes.
• Send any Java method call to a background thread and handle the response with a JS callback.
• It detect method overloading, you can target various method signature.
• JVM to JS exception handling.
• Fast, It cache native reference, saving some JVM lookup time.

Need to be done.

• Non-empty constructor.
• Static class support.

For now i have test this plugin successfully with JDK 1.7 and JDK 8. If you want to give it a try just go to this repo.

Before:
szero . --ci=true
After
szero . --ci

i started to use the .npm-init.js file and i noticed that when i call npm init -y i still get asked questions instead of just choosing all the defaults for me

#15

If there is already a test directory in $CWD when running npm init, the process fails with.

npm ERR! EEXIST: file already exists, mkdir 'test'

Put some stuff in GUIDELINES.md that helps guide releasing an NPM module, including recommendations for tagging, etc.

• Setup
• Openshift Origin
• Explore [overview] REST API
• How much control did you have over the version of node you used?
• What about ongoing development?
• What is the workflow like?
• What is required to see and test changes locally?

We need to have at least a basic idea about the meaning to be able to:

• See the result using hawkular-ui
• The minimum of the data working like the screenshots

https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/apiref/rest-apm.html#_fragments

They are a commercial company but provide some open source tools that perform static code analysis in order to identify known security vulnerabilities. Currently we recommend using [nsp](https://github.com/bucharest-gold/entente/blob/master/GUIDELINES.md#security) for this. We should determine if there is any reason to consider snyk over our current process.

Snyk has an open source component: https://github.com/Snyk/snyk
Vulnerabilities DB: https://github.com/Snyk/vulndb

When npm init is run, it is possible to use a custom script to prompt the user and supply defaults. First, users will need to set this value.

$ npm config set init-module ~/.npm-init.js

The .npm-init.js script might look something like this.

var cp = require('child_process');  
var priv;

var USER = process.env.GITHUB_USERNAME || 'YOUR_GITHUB_USERNAME';

module.exports = {

  name: prompt('name', basename || package.name),

  version: '0.0.1',

  private: prompt('private', 'true', function(val){
    return priv = (typeof val === 'boolean') ? val : !!val.match('true')
  }),

  create: prompt('create github repo', 'yes', function(val){
    val = val.indexOf('y') !== -1 ? true : false;

    if(val){
      console.log('enter github password:');
      cp.execSync("curl -u '"+USER+"' https://api.github.com/user/repos -d " +
        "'{\"name\": \""+basename+"\", \"private\": "+ ((priv) ? 'true' : 'false')  +"}' ");
      cp.execSync('git remote add origin '+ 'https://github.com/'+USER+'/' + basename + '.git');
    }

    return undefined;
  }),

  main: prompt('entry point', 'index.js'),

  repository: {
    type: 'git',
    url: 'git://github.com/'+USER+'/' + basename + '.git' },

  bugs: { url: 'https://github.com/'+USER'/' + basename + '/issues' },

  homepage: "https://github.com/"+USER+"/" + basename,

  keywords: prompt(function (s) { return s.split(/\s+/) }),

  license: 'MIT',

  cleanup: function(cb){

    cb(null, undefined)
  }

}

See: https://nodesource.com/blog/eleven-npm-tricks-that-will-knock-your-wombat-socks-off/

We need to release roi because:

tagged this 22 days ago · 13 commits to master since this tag
and this:
bucharest-gold/roi#15

• Simplifies a bit our start-stop bash scripts.
• If we delete the project directory no need download keycloak again.

Tracking issue for our ongoing Node.js upstream collaboration efforts.

[edit: simplified description]

https://github.com/bucharest-gold/szero/milestone/3

• Conference http://budapest.nodeconf.com/
• Dates: January 20, 2017
• Submission Link: https://github.com/nodeconf/budapest/issues/new
• Accepted: Unknown

A View Into the Vortex, or Tracing Asynchronous Operations in Node

Description

Tracing asynchronous code paths in Node.js is really hard. This makes it difficult to understand what is going wrong when your application blows up. Since Node.js version 4.0, however, Node has included the AsyncWrap API. In this talk you will learn how you can use the API to to gain a better understanding of what went wrong when your application fails, and where potential asynchronous processing bottlenecks are lurking.

Learning objectives

I will be presenting the AsyncWrap API in an overview format, with some discussion of the potential usages of the API in user applications and custom frameworks. I will review some existing modules that provide an abstraction layer over this low-level API, and demonstrate the development of a long stack trace module, making use of the API.

City of residence

Asheville, North Carolina, USA

keycloak/keycloak-nodejs-connect#19 (comment)

Include those sexy screenshots and how others could use the tool to check their own dependencies.

https://github.com/bucharest-gold/szero/milestone/2

Explain a little about what the plot-timer-events tool shows, and how we can use it to optimize our tools/modules.

I know we are also focused on Node core involvement, but we should possibly also take a look at npm and its issues. https://github.com/npm/npm/issues

considering this is "the" way to interact with node modules.

My tweet asking npmjs were to start: https://twitter.com/sienaluke/status/758330112047779840

This was also a good primer on npm and some of its usage, https://youtu.be/hopWbVKmiVQ?list=PLfMzBWSH11xZWvE3iuTw6tdzp90gnODdp

Some things to improve:

• Add service discovery
• Add circuit breaker
• Modern node version

Title changed from "Implement" to "Define improvements" since implementation is a multi-step process. See additional related work.

Ref: #93