Joe Dooley joedooley

Who is this Gist for?

This Gist demonstrates an approach to removing a specific user's data from an Amazon DynamoDB table that was created as an AWS AppSync data source. It may be helpful for those who need to remove records that are associated with a Cognito User that will be deleted from their Cognito User Pool.

Steps to clean up user data

Clean up user data with DataStore disabled (conflict resolution disabled)

Assuming you have this schema

Pure ESM package

The package linked to from here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

Use ESM yourself. (preferred)
Use import foo from 'foo' instead of const foo = require('foo') to import the package. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

Contract Killer

The popular open-source contract for web professionals by Stuff & Nonsense

Originally published: 23rd December 2008
Revised date: March 15th 2016
Original post

	import { getSession } from './getMiddlewareSession';
	import { NextMiddleware } from 'next/server';

	const middleware: NextMiddleware = async (req, event) => {
	try {
	let session = await getSession(req)
	console.log(session.user.name)
	} catch (err) {
	console.error(err)
	}

	/* eslint-disable prefer-template */

	const path = require('path');
	const aliases = require('./aliases');

	// ///////////////////////////////////////////////////////////////
	// ////////////////// PLUGINS ////////////////////////////////
	// ///////////////////////////////////////////////////////////////

	const commonPlugins = [

	'use strict';

	module.exports = function CustomError(message, extra) {
	Error.captureStackTrace(this, this.constructor);
	this.name = this.constructor.name;
	this.message = message;
	this.extra = extra;
	};

	require('util').inherits(module.exports, Error);

	Secure sessions are easy, but not very well documented.
	Here's a recipe for secure sessions in Node.js when NginX is used as an SSL proxy:

	The desired configuration for using NginX as an SSL proxy is to offload SSL processing
	and to put a hardened web server in front of your Node.js application, like:

	[NODE.JS APP] <- HTTP -> [NginX] <- HTTPS -> [PUBLIC INTERNET] <-> [CLIENT]

	Edit for express 4.X and >: Express no longer uses Connect as its middleware framework, it implements its own now.

	cd ~/
	mkdir .localhost-ssl

	sudo openssl genrsa -out ~/.localhost-ssl/localhost.key 2048
	sudo openssl req -new -x509 -key ~/.localhost-ssl/localhost.key -out ~/.localhost-ssl/localhost.crt -days 3650 -subj /CN=localhost
	sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain ~/.localhost-ssl/localhost.crt

	npm install -g http-server
	echo "
	function https-server() {

	import React from "react";
	import Counter from "./Counter";

	const App = () => {
	return (
	<div className="App">
	<Counter initialCount={100} />
	</div>
	);
	};