https://github.com/ehmicky/cross-platform-node-guide/blob/master/README.md

• shorter time to first paint
• better font loading
• Node: retry requests automatically
  • Also here
• Node: handle uncaught Promise exceptions with a generic handler
• Node best practices
• More Node best practices
• Front end performance
• Node security best practices
• Put a name and description in every file containing code (what’s the file for?)
• Project Guidelines
• use void for IIFEs
• Security: cookies should use sameSite and httpOnly settings by default
• Front-end performance checklist
• Be conservative in what you do, liberal in what you accept (i.e. allow flexible input but consistent output)
• npm install should deploy everything a developer needs to start work on the project
• lint files as part of test process
• check meta tags
• Use semantic CSS class names (e.g. cup-handle) rather than descriptive ones (e.g. red)
• Use flex-basis to force a flex row to wrap on narrow screens (avoids a need for media queries)
• Design should be responsive both horizontally and vertically (don’t let items take up too much or little vertical screen space, on narrow or wide devices)
• Use defaults with CSS variables
• web fonts
• other method for measuring Node request times
• Vox accessibility guidelines

Add your html2element utility (from the Lotus app).

• Request Logging

Gather checklist items from this book

This should include lists of resources for math and various programming languages.

Collect all your resource lists from various places.

http://alistapart.com/article/the-best-request-is-no-request-revisited

https://hackernoon.com/rethinking-javascript-eliminate-the-switch-statement-for-better-code-5c81c044716d

Use an MIT license, but specify the source and license for Stefan's R diagrams.

Checklist Items for Express Apps on Azure

package.json

• The "main" field should point to the entry point for the app (usually app.js)

• Node engines should be specified in the "engines" field

app.js settings

• do init and config in separate files, e.g.:

  • authenticate.js
  • config.js
  • errors.js
  • handlebars.js
  • limiter.js
  • logger.js
  • mendeley.js
  • passport.js
  • router.js
  • server.js
  • socket.js

• trust proxy

  app.enable(`trust proxy`);

• declare Handlebars engine and file extension

  app.engine(extname, handlebars.engine);

• log server information when app starts

  • Server started. Press Ctrl+C to terminate.
  • Project
  • Port
  • Time
  • Node Version
  • Env

Middleware

• authentication (if needed)

• helmet - security

• rate limiting (e.g. with express-rate-limit)

• routing for static files

  express.static(path.join(__dirname, `/public`));

Logging & Error Handling

• 404 and 500 handlers (should come last in the waterfall)

  // 404 handler
  const error404 = (req, res, next) => {
    // render error page with 404 status
  };
  
  // 500 handler
  const error500 = (err, req, res, next) => {
    // render error page with 500 status and error ID
    // log and report errors
  };

• generic error handler for server

  server.on(`error`, err => {
    // log and report error
  });

• standardized error handling

  • standardized messages (e.g. with Boom)
  • res.error middleware
  • convert errors from third-party services (be thorough)

• provide an option to log requested URL with an environment variable

  • The log should happen after static files are sent

• provide an option to log server errors with an environment variable

Use rel=preload

<link rel="preload" href="mystyles.css" as="style" onload="this.rel='stylesheet'">

Much like other attribute-toggling approaches above, rel="preload" will cause supporting browsers to download–but not apply–the referenced file, so again we need an onload handler to set the rel attribute to stylesheet once it finishes loading. This may not look like a big improvement over other approaches, but one advantage that rel="preload" brings is that supporting browsers will start downloading the file earlier than they would with say, a stylesheet with a non-matching media value.

Can you also just use the async attribute?

• Put each utility in a separate file
• Use JavaScript ES6 modules to export each utility to a main index.js file
• Include index.js in your projects, and import just the utilities you need

https://gethead.info/

Should accept any folder as input, and a path as output, and convert all the LESS files in the given folder (and only the LESS files). Should work as both a module and from the command line.

https://www.callingbullshit.org/syllabus.html

https://medium.com/@Abazhenov/using-async-await-in-express-with-node-8-b8af872c0016

Example 6-4. A classOf() function
function classOf(o) {
if (o === null) return "Null";
if (o === undefined) return "Undefined";
return Object.prototype.toString.call(o).slice(8,-1);
}

For each script:

• check for an already-published version
• delete the script from this repo if a published version exists
• create a new repo for the script if no suitable published version exists
  • make repo private if appropriate
• publish the script from the new repo to npm and gpr

The end result should be that this repo no longer contains any JavaScript scripts.

Other helpers that are available in handlebars-helpers shouldn't be added here.

function head(name, opts) {
  if (!this.head) this.head = {};
  this.head[name] = opts.fn(this);
  return null;
}

function md(text, inline) {
  // eslint-disable-next-line new-cap
  if (!text) return ``;
  const method = inline === `inline` ? `renderInline` : `render`;
  return new handlebars.SafeString(markdown[method](text));
}

function section(name, opts) {
  if (!this.sections) this.sections = {};
  this.sections[name] = opts.fn(this);
  return null;
}

• prefer Handlebars commenting for HTML (when appropriate)
• update inline code commenting after writing code
• all the items from the DLx MAINTAINERS checklist (add these to a general maintenance process checklist)

https://github.com/thedaviddias/Front-End-Checklist

langauge

const isDateString = dateString => Boolean(Date.parse(dateString));

Check whether a date string is valid.

https://github.com/Azure/azure-documentdb-js-server/blob/master/samples/stored-procedures/update.js

Then update this sproc in all your repositories

https://github.com/goldbergyoni/javascript-testing-best-practices/blob/master/readme.md

https://davidwalsh.name/essential-javascript-functions?utm_source=javascriptweekly&utm_medium=email