chrisguttandin / dynamo-db-local Goto Github PK

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.4.3 of sinon was just published.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 29.0.1 of eslint-config-holy-grail was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-holy-grail is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 31.0.1 of eslint-config-holy-grail was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-holy-grail is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

HI,

I'm using the package for my unit testing.

But when I start my tests it raises a DNS error :

Error: getaddrinfo ENOTFOUND dynamodb.test.amazonaws.com
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:71:26)

My teardown.ts

import { ChildProcess } from 'child_process';
import build from './index';

declare global {
    var dynamoProcess: ChildProcess | undefined;
}

export default async function() {
    const table = build().getTable();

    if (await table.exists()) {
        await table.deleteTable('DeleteTableForever');
    }

    if (global.dynamoProcess) {
        global.dynamoProcess.kill();
    }
};

My setup.ts:

import { ChildProcess } from 'child_process';
import build from './index';
// @ts-ignore
import local from 'dynamo-db-local';

export default async function () {
    global.dynamoProcess = local.spawn() as ChildProcess;
    await new Promise((resolve) => setTimeout(resolve, 1000));

    const table = build().getTable();

    if (!(await table.exists())) {
        await table.createTable();
    }
}

I don't understand why it trying to reach that dns 😅

Version 7.1.1 of @commitlint/cli was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@commitlint/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Thank you for this library!

When starting a new instance of the local DynamoDB instance using the command: 'docker', it launches without any problems:

    console.debug('Starting local DynamoDB with Docker');
    const pr = dynamoDBLocal.spawn({
      port: MAPPED_PORT,
      command: 'docker',
      path: null,
    });
    return {
      port: MAPPED_PORT,
      stop: async () => {
        pr.kill();
      },
    };

However, it seems that when calling kill on the spawned process, the Docker container continues to run.

Maybe adding the --init argument to the command for running Docker could resolve this issue?

The following code used to work on my older intel MacBook.

const AWS = require('aws-sdk');
const dynamoDbLocal = require('dynamo-db-local');

async function init() {
	var process = await dynamoDbLocal.spawn({
		port: 8888
	});

	const service = new AWS.DynamoDB({
		apiVersion: 		'2016-11-23',
		endpoint: 		"http://localhost:8888",
		region: 		'eu-west-1',
		sslEnabled:		false,
		accessKeyId:		'fake',
		secretAccessKey:	'fake',
	});

	const client = new AWS.DynamoDB.DocumentClient({
		service
	});

	result = await service.listTables().promise()
	console.log(result);
}

init();

But now I get the following error:

UnknownEndpoint: Inaccessible host: `localhost'. This service may not be available in the `eu-west-1' region.

So I'm wondering what the issue is here.

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency eslint-config-holy-grail was updated from 46.0.13 to 46.0.14.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-holy-grail is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi there and thanks for this lib! The recent v9 doesn't seem to be working:

Error: Unable to access jarfile ../lib/dynamodb_local_2024-04-16/DynamoDBLocal.jar

As far as I could see from the source code, it is referencing the jarfile from ../lib/, but the build code is creating build/node and build/es2019.

The createSpawn command is not considering now that there is a new subfolder inside build/, resulting in java trying to access build/lib/dynamodb_local_2024-04-16 instead of lib/dynamodb_local_2024-04-16

As a workaround, I'm using v8 here

There have been updates to the commitlint monorepo:

• • The devDependency @commitlint/cli was updated from 8.0.0 to 8.1.0.

• The devDependency @commitlint/config-angular was updated from 8.0.0 to 8.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the commitlint group definition.

commitlint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

There should be an option for this library to store the database data on disk instead of in memory. This would probably require changing up how options are passed into the spawn function (maybe allow passing in an object as well?)

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.4.7 of sinon was just published.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴