profile
viewpoint

hayd/deno-docker 323

Latest dockerfiles and images for deno - alpine, centos, debian, ubuntu

hayd/ctox 20

tox for conda

hayd/deno 2

A secure TypeScript runtime on V8

andrewdefries/chembrain 1

Learn chemistry through tactile play. Build intuition for molecules and chemistry by drawing and playing interactive d3.js visualizations in your browser.

altos-research/todo 0

An example play app to demonstrate the "Object Oriented Security" pattern.

hayd/9m 0

9m Unicode URL Shortener

hayd/angular-seed 0

Seed project for angular apps.

hayd/AnsiColor.jl 0

Formatting for ANSI colored strings in Julia

created taghayd/deno-lambda

tag1.2.3

A deno runtime for AWS Lambda. Deploy deno via SAM, serverless, or bundle it yourself.

created time in 18 hours

release hayd/deno-lambda

1.2.3

released time in 18 hours

push eventhayd/deno-lambda

Luca Casonato

commit sha e409131a79382b4ca3b0a008c0a00fcb0da31b56

Bump to Deno 1.2.3

view details

Andy Hayden

commit sha 700d74706a413e868a24e6cb7957127ae705f824

Fix tests by removing v prefix in std versioning

view details

Andy Hayden

commit sha be7f7371696f13f48e5674bec0072a5c152abac6

Merge pull request #97 from hayd/bump-1.2.3 Bump to Deno 1.2.3

view details

push time in 18 hours

delete branch hayd/deno-lambda

delete branch : bump-1.2.3

delete time in 18 hours

PR merged hayd/deno-lambda

Bump to Deno 1.2.3

cc @hayd

+25 -25

0 comment

18 changed files

lucacasonato

pr closed time in 18 hours

push eventhayd/deno-lambda

Andy Hayden

commit sha 700d74706a413e868a24e6cb7957127ae705f824

Fix tests by removing v prefix in std versioning

view details

push time in 18 hours

issue commenthayd/deno-docker

can't access my serivce

any thoughts on this @lucacasonato ? I haven't used docker-compose so am a little unsure about this issue.

Hi, I still can't access my service out of the container, but can do that in the container,

Is it something like a different port needs to be exposed?

guzhongren

comment created time in a day

issue closedhayd/deno-docker

how to use deno docker in gitlab runner?

this is the .gitlab-ci.yml file:

build:
  image:
    name: "hayd/debian-deno:latest"
  script:
    - echo hello

and gets the error:

Skipping Git submodules setup
Executing "step_script" stage of the job script
/bin/sh: 0: Can't open sh

If I add entrypoint like this:

build:
  image:
    name: "hayd/debian-deno:latest"
    entrypoint: ["/bin/sh"]
  script:
    - echo hello

still gets another error:

Skipping Git submodules setup
Executing "step_script" stage of the job script
error: Found argument 'sh' which wasn't expected, or isn't valid in this context

USAGE:
    deno [OPTIONS] [SUBCOMMAND]

For more information try --help

closed time in a day

xlambda

issue commenthayd/deno-docker

how to use deno docker in gitlab runner?

should be fixed in 1.2.3

xlambda

comment created time in a day

issue closedhayd/deno-docker

can't access my serivce

ENV

❯ docker version
Client: Docker Engine - Community
 Version:           19.03.12
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        48a66213fe
 Built:             Mon Jun 22 15:41:33 2020
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.12
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       48a66213fe
  Built:            Mon Jun 22 15:49:27 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683**

docker-compose.yaml

https://github.com/guzhongren/deno-restful-api-with-postgresql-tdd

Question

❯ docker-compose ps
                     Name                                   Command               State               Ports            
-----------------------------------------------------------------------------------------------------------------------
deno-restful-api-with-postgresql-tdd_db_1        docker-entrypoint.sh postgres    Up      0.0.0.0:5432->5432/tcp       
deno-restful-api-with-postgresql-tdd_pgadmin_1   /entrypoint.sh                   Up      443/tcp, 0.0.0.0:9099->80/tcp
deno-restful-api-with-postgresql-tdd_restful_1   deno run --allow-net --all ...   Up      0.0.0.0:9000->8000/tcp ****

when I start my compose, I can access my pgadmin,and postgresq, but I can't access my service written by deno; plz ,help me to find the cause; at the same times, I can request my health API in docker container, /api/v1/health

thx

closed time in a day

guzhongren

issue commenthayd/deno-docker

can't access my serivce

Please let me know if still an issue in 1.2.3

guzhongren

comment created time in a day

issue closedhayd/deno-docker

Add ${DENO_DIR}/bin to $PATH

When installing utilities to the global using deno install they then can't be used in the image directly.

The image needs a

ENV PATH="${DENO_DIR}/bin:${PATH}"

somewhere in it.

Also, I noticed that deno install doesn't install to DENO_DIR, it instead installs to /root/.deno/ which might be a separate issue.

closed time in a day

JonDum

created taghayd/deno-docker

tag1.2.3

Latest dockerfiles and images for deno - alpine, centos, debian, ubuntu

created time in a day

release hayd/deno-docker

1.2.3

released time in a day

push eventhayd/deno-docker

Luca Casonato

commit sha 57b66ad28200396e8136553e2d287ea07176206e

Bump to Deno 1.2.3

view details

Andy Hayden

commit sha e04b23749636a2441aea072383aa452e85e2de2a

Merge pull request #70 from lucacasonato/bump-1.2.3 Bump to Deno 1.2.3

view details

push time in a day

PR merged hayd/deno-docker

Bump to Deno 1.2.3

cc @hayd

+14 -14

0 comment

9 changed files

lucacasonato

pr closed time in a day

push eventhayd/deno-docker

Andy Hayden

commit sha 094c4cba6b179f96f02f57bde18030e860910e39

Add entry.sh and set DENO_INSTALL_ROOT

view details

Andy Hayden

commit sha 5cf67575eeea23b82106257c401c5ad92eae88d3

Move docker-entrypoint.sh to /usr/local/bin

view details

Andy Hayden

commit sha ddb40781df5223fb54def49a5961d29a4534f514

Merge pull request #69 from hayd/entry Add entry.sh and set DENO_INSTALL_ROOT

view details

push time in a day

delete branch hayd/deno-docker

delete branch : entry

delete time in a day

PR merged hayd/deno-docker

Add entry.sh and set DENO_INSTALL_ROOT

Closes #57 and #68.

I've added entry script as /.docker-entry.sh 🤷 , perhaps there is a better choice...?

cc @lucacasonato

+39 -8

0 comment

9 changed files

hayd

pr closed time in a day

issue closedhayd/deno-docker

Don't use deno as entrypoint

I think it should be a docker-entrypoint.sh file, like node does.

This would allow using the image for launching other kind of scripts, and allowing Gitlab CI to work, for example.

I cant PR if you want. Cheers!

closed time in a day

DanielRamosAcosta

push eventhayd/deno-docker

Andy Hayden

commit sha 5cf67575eeea23b82106257c401c5ad92eae88d3

Move docker-entrypoint.sh to /usr/local/bin

view details

push time in a day

PR opened hayd/deno-docker

Add entry.sh and set DENO_INSTALL_ROOT

Closes #57 and #68.

I've added entry script as /.docker-entry.sh 🤷 , perhaps there is a better choice...?

cc @lucacasonato

+37 -8

0 comment

8 changed files

pr created time in 2 days

push eventhayd/deno-docker

Luca Casonato

commit sha e9705df72018759648ca6e31a341fed25dd9c02f

Bump to Deno 1.2.1 (#63)

view details

杨俊宁

commit sha 067af17fa7939a4bdd83e37216d31c9685803ede

Update README.md

view details

Luca Casonato

commit sha 8cf2ca33273b129a962c91b0b1adb4428c9974f7

Bump to 1.2.2

view details

Luca Casonato

commit sha e2b15c4d6428766794a662cbbbe1e7845d7432b9

Update rust to 1.45.0

view details

Andy Hayden

commit sha baa555406ab312c17d0d865c5c68a80315137d71

Merge pull request #66 from lucacasonato/bump-1.2.2 chore: bump to Deno 1.2.2

view details

杨俊宁

commit sha 09c2d082cfc489d240563d9b3580981ca1cbd02f

Merge branch 'master' into patch-1

view details

Andy Hayden

commit sha 2894b1c92d763c55014885d0bbf7d9e7684b1fa2

Merge pull request #64 from youngjuning/patch-1 fix comment error

view details

Thomas B Homburg

commit sha 14aef14027c8e28c61b098188a8b807f58cb4c67

Add deno `run` command to docker run example

view details

Andy Hayden

commit sha 44c957526b1681cb084853897c902fde5b3c931c

Merge pull request #67 from homburg/patch-1 Add deno `run` command to docker run example

view details

Andy Hayden

commit sha 094c4cba6b179f96f02f57bde18030e860910e39

Add entry.sh and set DENO_INSTALL_ROOT

view details

push time in 2 days

push eventhayd/deno-docker

Andy Hayden

commit sha a4a09e9769f88a1126ec65dd406da784843a156e

Add entry.sh and set DENO_INSTALL_ROOT

view details

push time in 2 days

create barnchhayd/deno-docker

branch : entry

created branch time in 2 days

issue commenthayd/deno-docker

Add ${DENO_DIR}/bin to $PATH

This seems reasonable (that deno install should work). cc @lucacasonato what do you think?

The doc reads:

The installation root is determined, in order of precedence:
  - --root option
  - DENO_INSTALL_ROOT environment variable
  - $HOME/.deno

Should DENO_INSTALL_ROOT be set to /usr/local/ or /opt/ ? 🤔 (That seems cleaner that modifying PATH.)

JonDum

comment created time in 3 days

push eventhayd/deno-docker

Thomas B Homburg

commit sha 14aef14027c8e28c61b098188a8b807f58cb4c67

Add deno `run` command to docker run example

view details

Andy Hayden

commit sha 44c957526b1681cb084853897c902fde5b3c931c

Merge pull request #67 from homburg/patch-1 Add deno `run` command to docker run example

view details

push time in 3 days

PR merged hayd/deno-docker

Add deno `run` command to docker run example

Could not get the docker run example to work without adding a run command arguments to deno

+1 -1

1 comment

1 changed file

homburg

pr closed time in 3 days

pull request commenthayd/deno-docker

Add deno `run` command to docker run example

oops! Thank you @homburg !

homburg

comment created time in 3 days

issue commentdenoland/deno_registry2

camelCase or snake_case?

The Deno style guide specifies underscores for file names.

Yeah, it is the same issue, but that style suggestion is... surprising. (The same question applies: "why not hyphens?", I suspect the answer is "ry prefers underscores in filenames". 🤷 )

Personally I uses hyphens unless there is a need for separators in the filename then I use underscore too e.g. topic_file-name_YYYY-MM-DD.csv e.g. perhaps in lieu of directory structure (topic/YYYY-MM-DD/file-name.csv) or otherwise.

mesqueeb

comment created time in 6 days

issue commentdenoland/deno_registry2

camelCase or snake_case?

IME kebab-case also had the benefit of google ability, but perhaps it's a bit late to select that? https://stackoverflow.com/questions/10302179/hyphen-underscore-or-camelcase-as-word-delimiter-in-uris

I wonder if there should be some kind of string distance function applied against existing libraries (so you can say "this new module name you're proposing is too close xxx").

mesqueeb

comment created time in 7 days

Pull request review commentdeno-postgres/deno-postgres

chore:transaction processing single conn

 export { } from "https://deno.land/std@0.61.0/async/deferred.ts";  export { Hash } from "https://deno.land/x/checksum@1.2.0/mod.ts";++export {+  log,+} from "https://deno.land/x/mysql/src/logger.ts";

I don't think log should be included, the thrown error should suffice. (Aside: import urls should always be versioned.)

tksilicon

comment created time in 7 days

Pull request review commenthayd/deno-docker

chore: bump to Deno 1.2.2

 RUN curl -fL https://github.com/llvm/llvm-project/releases/download/llvmorg-10.0   && mv /tmp/clang+llvm-10.0.0-x86_64-linux-sles11.3 /tmp/clang ENV PATH=/tmp/clang-llvm/bin:$PATH -ENV RUST_VERSION=1.44.0+ENV RUST_VERSION=1.45.0 RUN curl https://sh.rustup.rs -sSf \   | sh -s -- --default-toolchain ${RUST_VERSION} -y ENV PATH=/root/.cargo/bin:$PATH -ENV DENO_VERSION=1.2.1+ENV DENO_VERSION=1.2.2  RUN curl -fsSL https://github.com/denoland/deno/releases/download/v${DENO_VERSION}/deno_src.tar.gz \   --output deno.tar.gz \   && tar -zxf deno.tar.gz \   && rm deno.tar.gz  RUN yum install -y gcc-c++ libatomic-RUN echo "INPUT ( /usr/lib64/libatomic.so.1.2.1 )" \+RUN echo "INPUT ( /usr/lib64/libatomic.so.1.2.2 )" \

Oh, this was a sed error I guess. The fact it wasn't necessary is interesting... Presumably one of the many lambda tests would have failed if it were.

Hmm!

lucacasonato

comment created time in 9 days

Pull request review commenthayd/deno-docker

chore: bump to Deno 1.2.2

 RUN curl -fL https://github.com/llvm/llvm-project/releases/download/llvmorg-10.0   && mv /tmp/clang+llvm-10.0.0-x86_64-linux-sles11.3 /tmp/clang ENV PATH=/tmp/clang-llvm/bin:$PATH -ENV RUST_VERSION=1.44.0+ENV RUST_VERSION=1.45.0 RUN curl https://sh.rustup.rs -sSf \   | sh -s -- --default-toolchain ${RUST_VERSION} -y ENV PATH=/root/.cargo/bin:$PATH -ENV DENO_VERSION=1.2.1+ENV DENO_VERSION=1.2.2  RUN curl -fsSL https://github.com/denoland/deno/releases/download/v${DENO_VERSION}/deno_src.tar.gz \   --output deno.tar.gz \   && tar -zxf deno.tar.gz \   && rm deno.tar.gz  RUN yum install -y gcc-c++ libatomic-RUN echo "INPUT ( /usr/lib64/libatomic.so.1.2.1 )" \+RUN echo "INPUT ( /usr/lib64/libatomic.so.1.2.2 )" \

Not sure I want to know how you worked this out 😳

lucacasonato

comment created time in 9 days

issue openedhayd/deno-udd

Use meta versions

e.g. https://cdn.deno.land/deno/meta/versions.json

(rather than gross rate-limitable hack...)

created time in 9 days

created tagdeno-postgres/deno-postgres

tagv0.4.3

PostgreSQL driver for Deno

created time in 9 days

release deno-postgres/deno-postgres

v0.4.3

released time in 9 days

push eventdeno-postgres/deno-postgres

Nicolas Guerrero

commit sha a0e91b5a7a9a0981e9df3972f52d6ef1f9e69a92

Bump Deno to v1.2.2, replace checksum lib for std/hash

view details

Andy Hayden

commit sha 85f0aeceb7d7ab74020f5d647e60673ae1528b64

Merge pull request #159 from Soremwar/deno_v1.2.2 Bump Deno to v1.2.2, replace checksum lib for std/hash

view details

push time in 9 days

PR merged deno-postgres/deno-postgres

Bump Deno to v1.2.2, replace checksum lib for std/hash
  • Replaced x/checksum library for std/hash implementation
  • Upgraded Deno to v1.2.2 and std to v0.63.0

Important

Please add a release tag to this so people don't have to pull from master or commit hash (Real shocking images) image

+9 -12

3 comments

5 changed files

Soremwar

pr closed time in 9 days

pull request commentdeno-postgres/deno-postgres

Bump Deno to v1.2.2, replace checksum lib for std/hash

Great, thanks @Soremwar , will tag after merge!

Soremwar

comment created time in 9 days

issue commenthayd/deno-docker

can't access my serivce

Should the command be run --allow-net ... (drop the deno prefix).

(This will be fixed with #57 - deno run should also work, I have a version of this on machine but have not yet created a PR...)

guzhongren

comment created time in 9 days

push eventhayd/deno-docker

杨俊宁

commit sha 067af17fa7939a4bdd83e37216d31c9685803ede

Update README.md

view details

杨俊宁

commit sha 09c2d082cfc489d240563d9b3580981ca1cbd02f

Merge branch 'master' into patch-1

view details

Andy Hayden

commit sha 2894b1c92d763c55014885d0bbf7d9e7684b1fa2

Merge pull request #64 from youngjuning/patch-1 fix comment error

view details

push time in 9 days

PR merged hayd/deno-docker

fix comment error
+2 -1

1 comment

1 changed file

youngjuning

pr closed time in 9 days

pull request commenthayd/deno-docker

fix comment error

Thanks @youngjuning!

youngjuning

comment created time in 10 days

push eventhayd/deno-docker

Luca Casonato

commit sha 8cf2ca33273b129a962c91b0b1adb4428c9974f7

Bump to 1.2.2

view details

Luca Casonato

commit sha e2b15c4d6428766794a662cbbbe1e7845d7432b9

Update rust to 1.45.0

view details

Andy Hayden

commit sha baa555406ab312c17d0d865c5c68a80315137d71

Merge pull request #66 from lucacasonato/bump-1.2.2 chore: bump to Deno 1.2.2

view details

push time in 10 days

PR merged hayd/deno-docker

Reviewers
chore: bump to Deno 1.2.2

cc @hayd

+15 -15

1 comment

9 changed files

lucacasonato

pr closed time in 10 days

pull request commenthayd/deno-docker

chore: bump to Deno 1.2.2

Looks like need to update rust version! Bleeding edge 😁

lucacasonato

comment created time in 10 days

issue commentdenoland/deno

Docker : Create official image

Just to note, if there is some suggestion this is important/useful for Official Images, @lucacasonato is a maintainer of hayd/deno-docker and also a member of denoland.

Anyway, perhaps let's move this discussion there for now.

zekth

comment created time in 11 days

issue commentdenoland/deno

Docker : Create official image

Permission is not a prerequisite... at least it's not mentioned in the docs.

I'm happy to take any feedback in order for hayd/deno-docker to meet any Official requirements, please create separate GH issues on that repo. That way we could more easily move it to denoland or Docker Official in the future.

(@ry Atm updates are bumping the version number and tagging releases, so docker would be much less arduous than vscode... But it would still be "another thing" to maintain!)

zekth

comment created time in 11 days

issue commentdenoland/deno

Docker : Create official image

I see (the original link you posted)

it is preferable to have upstream software authors maintaining their corresponding Official Images

This reads like it's a good start for dockerfiles to be moved to denoland if we want a deno Official Image in the future.

zekth

comment created time in 12 days

issue commentdenoland/deno

Docker : Create official image

When you say "project member" do you mean of deno(land)? or a member of the docker official images team?

zekth

comment created time in 12 days

startedritchie46/polars

started time in 12 days

issue commentdenoland/deno

Docker : Create official image

I’m not sure if that makes much sense if it doesn’t follow the official docker image guidelines

Are there some specific things hayd/docker-deno images are doing/not doing? Either way we can address these as GitHub issues ...

Atm it seems like there's been no indication the correct docker team is watching/interested in managing a deno image (yet).

Moving to denoland seems positive way forward.

zekth

comment created time in 12 days

Pull request review commentdenoland/deno

feat: add __STD_VERSION__ replacement variable in docs

 const p = Deno.run({     "deno",     "run",     "--allow-read",-    "https://deno.land/std/examples/cat.ts",+    "https://deno.land@__STD_VERSION__/examples/cat.ts",

typo (/std should not be removed)

lucacasonato

comment created time in 13 days

Pull request review commentdenoland/deno

feat(std/async): add asyncPool utility

+// Copyright 2018-2020 the Deno authors. All rights reserved. MIT license.++/**+ * pooledMap transforms values from an (async) iterable into another async+ * iterable. The transforms are done concurrently, with a max concurrency+ * defined by the poolLimit.+ * + * @param poolLimit The maximum count of items being processed concurrently. + * @param array The input array for mapping.+ * @param iteratorFn The function to call for every item of the array.+ */+export function pooledMap<T, R>(+  poolLimit: number,+  array: Iterable<T> | AsyncIterable<T>,+  iteratorFn: (data: T) => Promise<R>,+): AsyncIterableIterator<R> {

There is this related data structure DeferredStack https://github.com/deno-postgres/deno-postgres/blob/28249fbec10f7f1581f405a5a5b4b105a838629b/deferred.ts

basically you hand over a T when one is available (in deno-postgres T is a Client, essentially a db connection), and you can do something like:

const results = []
const pool = DeferredStack<undefined>(2, [undefined, undefined])  // here T is undefined
for await (const url of urls)) {
  await pool.pop()
  fetch(url)
    .then(x => results.push(x))
    // "release"
    .finally(x => pool.push(undefined))
}
// note this may be out of order
console.log(await Promise.all(results))

This datastructure allows pool.query(sql) to hide the connection being locked/released.

It feels like there should be a nice abstraction to this (with a clean for await api)...

lucacasonato

comment created time in 15 days

push eventhayd/deno-udd

Russell Clarey

commit sha eb70de197ed219b37e2034067cf917687e763fc1

update install cmd & add new registries to README

view details

Andy Hayden

commit sha f820e89632253631a46fa78e7ee5e2219cd72db2

Merge pull request #23 from rclarey/patch-1 Update install command & add new registries to README

view details

push time in 15 days

PR merged hayd/deno-udd

Update install command & add new registries to README

@hayd

+3 -1

0 comment

1 changed file

rclarey

pr closed time in 15 days

Pull request review commentdenoland/deno

feat(std/async): add asyncPool utility

+// Copyright 2018-2020 the Deno authors. All rights reserved. MIT license.++// From https://github.com/rxaviers/async-pool/blob/master/lib/es7.js.+// Copyright (c) 2017 Rafael Xavier de Souza http://rafael.xavier.blog.br+// Licensed under MIT++/**+ * asyncPool is like Promise.all(array.map(async () => {...})), except that you+ * can specify the maximum amount of items being processed concurrently.+ * + * @param poolLimit The maximum count of items being processed concurrently. + * @param array The input array for mapping.+ * @param iteratorFn The function to call for every item of the array.+ */+export async function asyncPool<T, R>(+  poolLimit: number,+  array: T[],+  iteratorFn: (data: T, array: T[]) => Promise<R>,

Why does the iteratorFn need to have array passed (rather than only data: T)?

lucacasonato

comment created time in 16 days

pull request commenthayd/deno-udd

add registries for jsdelivr and nestland

Hmm, I guess we should also add these to the README!

rclarey

comment created time in 19 days

push eventhayd/deno-udd

rclarey

commit sha d86eadae1229d0c6485c119a19766746d21c2e1a

add registries for jsdelivr and nestland

view details

Andy Hayden

commit sha 738c8c6ff167fd464f4b675d39e4a2282f034fd2

Merge pull request #21 from rclarey/add-jsdelivr-and-nestland add registries for jsdelivr and nestland

view details

push time in 19 days

PR merged hayd/deno-udd

add registries for jsdelivr and nestland

Closes #18 and closes #20.

@hayd

+120 -1

1 comment

2 changed files

rclarey

pr closed time in 19 days

issue closedhayd/deno-udd

Add support for x.nest.land URLs

These come in the form https://x.nest.land/package_name@#.#.#/entry.file. For example: https://x.nest.land/maze_generator@0.1.0/mod.js

closed time in 19 days

TheWizardBear

issue closedhayd/deno-udd

Add jsdelivr.net to supported module hosts

Great lib! We use https://cdn.jsdelivr.net/gh/{githubURL} for grabbing our modules. Would you mind adding that as a supported host?

closed time in 19 days

shah

pull request commenthayd/deno-udd

add registries for jsdelivr and nestland

Fantastic, thanks!

rclarey

comment created time in 19 days

push eventhayd/deno-lambda

dependabot[bot]

commit sha 8399f5cb975c32895ab4b06a41e387eae71875b4

Bump lodash from 4.17.15 to 4.17.19 in /example-aws-cdk Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.19. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](https://github.com/lodash/lodash/compare/4.17.15...4.17.19) Signed-off-by: dependabot[bot] <support@github.com>

view details

Andy Hayden

commit sha ed54a5ff2d861cb3a77ad7529b4079f8d118a999

Merge pull request #94 from hayd/dependabot/npm_and_yarn/example-aws-cdk/lodash-4.17.19 Bump lodash from 4.17.15 to 4.17.19 in /example-aws-cdk

view details

push time in 22 days

delete branch hayd/deno-lambda

delete branch : dependabot/npm_and_yarn/example-aws-cdk/lodash-4.17.19

delete time in 22 days

PR merged hayd/deno-lambda

Bump lodash from 4.17.15 to 4.17.19 in /example-aws-cdk dependencies

Bumps lodash from 4.17.15 to 4.17.19. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lodash/lodash/releases">lodash's releases</a>.</em></p> <blockquote> <h2>4.17.16</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li><a href="https://github.com/lodash/lodash/commit/1144918f3578a84fcc4986da9b806e63a6175cbb"><code>1144918</code></a> Rebuild lodash and docs</li> <li><a href="https://github.com/lodash/lodash/commit/3a3b0fd339c2109563f7e8167dc95265ed82ef3e"><code>3a3b0fd</code></a> Bump to v4.17.16</li> <li><a href="https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12"><code>c84fe82</code></a> fix(zipObjectDeep): prototype pollution (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4759">#4759</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/e7b28ea6cb17b4ca021e7c9d66218c8c89782f32"><code>e7b28ea</code></a> Sanitize sourceURL so it cannot affect evaled code (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4518">#4518</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/0cec225778d4ac26c2bac95031ecc92a94f08bbb"><code>0cec225</code></a> Fix lodash.isEqual for circular references (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4320">#4320</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4515">#4515</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/94c3a8133cb4fcdb50db72b4fd14dd884b195cd5"><code>94c3a81</code></a> Document matches* shorthands for over* methods (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4510">#4510</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4514">#4514</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.19">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~mathias">mathias</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

1 comment

1 changed file

dependabot[bot]

pr closed time in 22 days

pull request commenthayd/deno-lambda

Bump lodash from 4.17.15 to 4.17.19 in /example-aws-cdk

Well, that's clever! 😍

cc @turlockmike , xlink #90.

dependabot[bot]

comment created time in 22 days

Pull request review commenthayd/deno-lambda

CDK Example

+# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.+# yarn lockfile v1+++"@aws-cdk/assert@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/assert/-/assert-1.48.0.tgz#186a1e539eafe8aaad83fdb063bf3c4eb3429595"+  integrity sha512-orbpID/ERMsNq+yH+UIbkQ8u/PIYMC2UQ3YDbV1EDAyXI5F8ASBKxEXVJLXvUB2TbB1LXafZmcI9LffYBr/Vlg==+  dependencies:+    "@aws-cdk/cloud-assembly-schema" "1.48.0"+    "@aws-cdk/cloudformation-diff" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    "@aws-cdk/cx-api" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/assets@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/assets/-/assets-1.48.0.tgz#1ee87abc5744e53ad810db5d939324ea0e8e0b83"+  integrity sha512-gZQLZ4gVXApg85NYI9RYwPU21AB/0peJ+kn5mzJVrrOMNoR4aC3fVugDbcpBpf/eUKQ3CjnJG8DCHH8pka7XVg==+  dependencies:+    "@aws-cdk/core" "1.48.0"+    "@aws-cdk/cx-api" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-apigateway@^1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-apigateway/-/aws-apigateway-1.48.0.tgz#8b08c98149b57495f05a34a2e0cc351170e10050"+  integrity sha512-z2iPD7mysATo1SD4bYo4z5pnGkYqlv9x7+Cf6g6y95AsiBlsRuWQN6/OHcZDR6WIIiGxkz/9ElDaIEJ3o6B0kg==+  dependencies:+    "@aws-cdk/assets" "1.48.0"+    "@aws-cdk/aws-certificatemanager" "1.48.0"+    "@aws-cdk/aws-ec2" "1.48.0"+    "@aws-cdk/aws-elasticloadbalancingv2" "1.48.0"+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/aws-lambda" "1.48.0"+    "@aws-cdk/aws-logs" "1.48.0"+    "@aws-cdk/aws-s3" "1.48.0"+    "@aws-cdk/aws-s3-assets" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    "@aws-cdk/cx-api" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-certificatemanager@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-certificatemanager/-/aws-certificatemanager-1.48.0.tgz#f02e2c0cdec810452d9ca38529d0e1bff60588ff"+  integrity sha512-s72DPrq/yYYwmD6uR7+o4BPRaqSR2FHrnwi6oVEYquf/X5xfVXdp7NgYdw7utt/m05cNqH3N6hrGsFdTi8NubQ==+  dependencies:+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/aws-lambda" "1.48.0"+    "@aws-cdk/aws-route53" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-cloudwatch@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-cloudwatch/-/aws-cloudwatch-1.48.0.tgz#04f1d3f9fec0af51bea0b0dce0a81fa4603d8b6e"+  integrity sha512-8gouBTmwEdY/u5L3qmSjld4s852PumPBJlRWHy7eAbsyNGqu2EIdnL+RdAMsG2vccQAHusfQ8tPKQ/ZAQvhlAQ==+  dependencies:+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-ec2@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-ec2/-/aws-ec2-1.48.0.tgz#1202806f9387df1081e1a16e2e0187fff1675dcd"+  integrity sha512-mfuAOuhdqLe8QM9OMcoaQ2i/5rhG9q3rOe5gXjSHHdi7jVstw5gsrWTszt/bk4cAWtExV0k2A13X0554nSR5aA==+  dependencies:+    "@aws-cdk/aws-cloudwatch" "1.48.0"+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/aws-kms" "1.48.0"+    "@aws-cdk/aws-logs" "1.48.0"+    "@aws-cdk/aws-s3" "1.48.0"+    "@aws-cdk/aws-ssm" "1.48.0"+    "@aws-cdk/cloud-assembly-schema" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    "@aws-cdk/cx-api" "1.48.0"+    "@aws-cdk/region-info" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-elasticloadbalancingv2@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-elasticloadbalancingv2/-/aws-elasticloadbalancingv2-1.48.0.tgz#63d72b536061e1e8793485c91b3de4c25daa0cd2"+  integrity sha512-c4LRCht1nZSbw5TMkOsTVfapwP3i9AHIs3aNO+6dbcGsb4iZz31bzk+OSoMiD54mSp/amKU7TPtpTbNP/BkzlQ==+  dependencies:+    "@aws-cdk/aws-certificatemanager" "1.48.0"+    "@aws-cdk/aws-cloudwatch" "1.48.0"+    "@aws-cdk/aws-ec2" "1.48.0"+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/aws-lambda" "1.48.0"+    "@aws-cdk/aws-s3" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-events@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-events/-/aws-events-1.48.0.tgz#1d8b641e78ce98a0533a0a11ab8f72af60900a6e"+  integrity sha512-vhNUdBIfYbEH5+/PQ70qtjnwHB3i74pe5mno0SekN9PZWqM0r0y8FNNym3XdLl4+o1Q44XDWNAEa8OQAvIBKwg==+  dependencies:+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-iam@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-iam/-/aws-iam-1.48.0.tgz#423ad95e30657a85e0db19318eba782f499337ba"+  integrity sha512-M8t0YhmpfZrupgeOz9EbP1Ai6IY01e4My6t/7JXdtD2HqNmCyJ80cSJnCDq9fMwxKOj+GIaIJq84eVa0uc1BBA==+  dependencies:+    "@aws-cdk/core" "1.48.0"+    "@aws-cdk/region-info" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-kms@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-kms/-/aws-kms-1.48.0.tgz#9f1db5991409ae0ac092a1cf9226ed3ce38bf6ea"+  integrity sha512-+dDkVkOJeO6+V+p6aEuS9Y73B4e6zNu4N3l7koCBd/hJpQT5bioU5gRQdHjMvSpVZe9valD/vw0cOCEKRol53g==+  dependencies:+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-lambda@1.48.0", "@aws-cdk/aws-lambda@^1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-lambda/-/aws-lambda-1.48.0.tgz#0a6c549bbad0a2d07e0809bf5f51e89e00cea3bd"+  integrity sha512-vBrU0MfFv8fUXElWP1IfucPxlZ/3gU8Ef0/lZBqi/q4pS1iAWlgeJyynk+gE4rM9fHgZzEh73DE1/D0DiFeYtg==+  dependencies:+    "@aws-cdk/aws-cloudwatch" "1.48.0"+    "@aws-cdk/aws-ec2" "1.48.0"+    "@aws-cdk/aws-events" "1.48.0"+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/aws-logs" "1.48.0"+    "@aws-cdk/aws-s3" "1.48.0"+    "@aws-cdk/aws-s3-assets" "1.48.0"+    "@aws-cdk/aws-sqs" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    "@aws-cdk/cx-api" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-logs@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-logs/-/aws-logs-1.48.0.tgz#9511c574409a0cc1cf7a5521e5f834d4956425d0"+  integrity sha512-NWc4MibrnTjRiOnv1L+uKxtfSFgqeBq1nPan0HIRNj9xE//hUKa5kmhhvWm3a1AEKkxHynoNx5KUi5Qta3G7zQ==+  dependencies:+    "@aws-cdk/aws-cloudwatch" "1.48.0"+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-route53@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-route53/-/aws-route53-1.48.0.tgz#96d7712881fe90b9cbac1e55a0ccd0b14a061e25"+  integrity sha512-dgCHomRYaMzOfnYPEpiYrkJcfnCqNrRAPjAFmjMIAJlnx/lzllHNKsUfJza0X7KVoeJsvBvOptZdZSRqV0ChSQ==+  dependencies:+    "@aws-cdk/aws-ec2" "1.48.0"+    "@aws-cdk/aws-logs" "1.48.0"+    "@aws-cdk/cloud-assembly-schema" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-s3-assets@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-s3-assets/-/aws-s3-assets-1.48.0.tgz#dd1f5276623a2c8d6541ca3de3193aa08039aa8b"+  integrity sha512-p4KKkvbEuG5KDvVRpG8835UG578JtX/+wZksPmolAALjkituqUcP2pRxheJsv+K96yR/xP4MGULGZwkmFy2e0Q==+  dependencies:+    "@aws-cdk/assets" "1.48.0"+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/aws-kms" "1.48.0"+    "@aws-cdk/aws-s3" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    "@aws-cdk/cx-api" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-s3@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-s3/-/aws-s3-1.48.0.tgz#6d9afd123fc4fb069cec26f8257fd60bd95bf638"+  integrity sha512-mGsJPjq5rninLA1bcoKRoY0bkKJZwPrOVz0FayaAxJpFdS0qWscZl1hcj3QkzyypWtcmraBXRp5uv0Dhm5YC1A==+  dependencies:+    "@aws-cdk/aws-events" "1.48.0"+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/aws-kms" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-sam@^1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-sam/-/aws-sam-1.48.0.tgz#081f3a7368bb47a49ddefd654b89e0fc8c250aad"+  integrity sha512-U895HQe5lStu13JocP3zVxTKj3SKfbIp9RTz2S7ZJUocwxLoSIN9p0Y1vR9D4dDdWDkQewxaxMmrUpM+f73N9Q==+  dependencies:+    "@aws-cdk/core" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-sqs@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-sqs/-/aws-sqs-1.48.0.tgz#13021aaa1b7b52eac84f08986d1a61ed9c90a93c"+  integrity sha512-R7bNOyCyyKOO02zUUnazpeLakINB6bWtqp1UyEUilOum+X3iUHJs/PORPVwKcArWAhxydGCB01xky/sQ7o6gjA==+  dependencies:+    "@aws-cdk/aws-cloudwatch" "1.48.0"+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/aws-kms" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/aws-ssm@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/aws-ssm/-/aws-ssm-1.48.0.tgz#c11f50a4f817c03c88a036e0a748931e7ae8062c"+  integrity sha512-KaUF+kwp9HjxRZ3NZsIuKhR9r8fAyfEYnc+nbsxglho4VZtS6Yv6ujiZfwSk/iE3SUuRVcwHR+GPOQs6KawnrQ==+  dependencies:+    "@aws-cdk/aws-iam" "1.48.0"+    "@aws-cdk/aws-kms" "1.48.0"+    "@aws-cdk/cloud-assembly-schema" "1.48.0"+    "@aws-cdk/core" "1.48.0"+    constructs "^3.0.2"++"@aws-cdk/cfnspec@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/cfnspec/-/cfnspec-1.48.0.tgz#76fab24db74a6ab057121e0f730b844b39e04e91"+  integrity sha512-Nj2Z2OtQTHEXAEaKB9rU/A1GG5uTmMmnBcC60TjrS+nSLhOZ4OspM+zC0NM1a5jw90he3vV3z8YLMi91KRXVOw==+  dependencies:+    md5 "^2.2.1"++"@aws-cdk/cloud-assembly-schema@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/cloud-assembly-schema/-/cloud-assembly-schema-1.48.0.tgz#8bfc674fd7cb6562cf75a88d7ffb9ada993d4241"+  integrity sha512-3+TSjB/3hmVfcEQ0g4hitdNqz68MpYaLZGJnoVef76pNJijGbPtVMcLP8/iZ8LiOwKtZlwH7OEzcmQzSklHuUw==+  dependencies:+    jsonschema "^1.2.5"+    semver "^7.2.2"++"@aws-cdk/cloudformation-diff@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/cloudformation-diff/-/cloudformation-diff-1.48.0.tgz#a4c940a0e93882ed8a65b2c3c8bb3f80ff739fbe"+  integrity sha512-jXNfuoC443zigi2RLtggfCwYscVPa9cHiiCZ1pXAmnRRNgcfjA7vg7K8/MPf0uHQL0pOAMale3FoV17oUooVSQ==+  dependencies:+    "@aws-cdk/cfnspec" "1.48.0"+    colors "^1.4.0"+    diff "^4.0.2"+    fast-deep-equal "^3.1.3"+    string-width "^4.2.0"+    table "^5.4.6"++"@aws-cdk/core@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/core/-/core-1.48.0.tgz#4dd125ab18f2772ddf79bca7f23c0654f297e486"+  integrity sha512-nPSLI/qa9kXxuspOAYTUqf2YUy83F+6QelC9/ZYz+NVwuzGL+YTQmG5NZCzuFWyla+NZX7Med/IXxGOpRMP6WQ==+  dependencies:+    "@aws-cdk/cloud-assembly-schema" "1.48.0"+    "@aws-cdk/cx-api" "1.48.0"+    constructs "^3.0.2"+    fs-extra "^9.0.1"+    minimatch "^3.0.4"++"@aws-cdk/cx-api@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/cx-api/-/cx-api-1.48.0.tgz#1df4c1bcf281b755e05550b1c863541c512eedd0"+  integrity sha512-zuL5AllIsnro2RnofJ0VpgvMaePLhJjBwY87P1yQ0BJuw3tMtmLI++WaJKj2jbzdu8eXgsHk0KwyA7yl+5DDIw==+  dependencies:+    "@aws-cdk/cloud-assembly-schema" "1.48.0"+    semver "^7.2.2"++"@aws-cdk/region-info@1.48.0":+  version "1.48.0"+  resolved "https://registry.yarnpkg.com/@aws-cdk/region-info/-/region-info-1.48.0.tgz#43eb7b1423b1d99cc5c17830e723e743481f1548"+  integrity sha512-e5f8rB5+4VYx0HYkTcWCerYEHHndJK5kZUpUvUS95qFRmMv1xvFSL9FeHYQ5hDgGQUEmxYMWFMHGgJDSCMiKXA==++"@types/color-name@^1.1.1":+  version "1.1.1"+  resolved "https://registry.yarnpkg.com/@types/color-name/-/color-name-1.1.1.tgz#1c1261bbeaa10a8055bbc5d8ab84b7b2afc846a0"+  integrity sha512-rr+OQyAjxze7GgWrSaJwydHStIhHq2lvY3BOC2Mj7KnzI7XK0Uw1TOOdI9lDoajEbSWLiYgoo4f1R51erQfhPQ==++"@types/node@10.17.5":+  version "10.17.5"+  resolved "https://registry.yarnpkg.com/@types/node/-/node-10.17.5.tgz#c1920150f7b90708a7d0f3add12a06bc9123c055"+  integrity sha512-RElZIr/7JreF1eY6oD5RF3kpmdcreuQPjg5ri4oQ5g9sq7YWU8HkfB3eH8GwAwxf5OaCh0VPi7r4N/yoTGelrA==++agent-base@4, agent-base@^4.2.0, agent-base@^4.3.0:+  version "4.3.0"+  resolved "https://registry.yarnpkg.com/agent-base/-/agent-base-4.3.0.tgz#8165f01c436009bccad0b1d122f05ed770efc6ee"+  integrity sha512-salcGninV0nPrwpGNn4VTXBb1SOuXQBiqbrNXoeizJsHrsL6ERFM2Ne3JUSBWRE6aeNJI2ROP/WEEIDUiDe3cg==+  dependencies:+    es6-promisify "^5.0.0"++agent-base@~4.2.1:+  version "4.2.1"+  resolved "https://registry.yarnpkg.com/agent-base/-/agent-base-4.2.1.tgz#d89e5999f797875674c07d87f260fc41e83e8ca9"+  integrity sha512-JVwXMr9nHYTUXsBFKUqhJwvlcYU/blreOEUkhNR2eXZIvwd+c+o5V4MgDPKWnMS/56awN3TRzIP+KoPn+roQtg==+  dependencies:+    es6-promisify "^5.0.0"++ajv@^6.10.2:+  version "6.12.2"+  resolved "https://registry.yarnpkg.com/ajv/-/ajv-6.12.2.tgz#c629c5eced17baf314437918d2da88c99d5958cd"+  integrity sha512-k+V+hzjm5q/Mr8ef/1Y9goCmlsK4I6Sm74teeyGvFk1XrOsbsKLjEdrvny42CZ+a8sXbk8KWpY/bDwS+FLL2UQ==+  dependencies:+    fast-deep-equal "^3.1.1"+    fast-json-stable-stringify "^2.0.0"+    json-schema-traverse "^0.4.1"+    uri-js "^4.2.2"++ansi-regex@^4.1.0:+  version "4.1.0"+  resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-4.1.0.tgz#8b9f8f08cf1acb843756a839ca8c7e3168c51997"+  integrity sha512-1apePfXM1UOSqw0o9IiFAovVz9M5S1Dg+4TrDwfMewQ6p/rmMueb7tWZjQ1rx4Loy1ArBggoqGpfqqdI4rondg==++ansi-regex@^5.0.0:+  version "5.0.0"+  resolved "https://registry.yarnpkg.com/ansi-regex/-/ansi-regex-5.0.0.tgz#388539f55179bf39339c81af30a654d69f87cb75"+  integrity sha512-bY6fj56OUQ0hU1KjFNDQuJFezqKdrAyFdIevADiqrWHwSlbmBNMHp5ak2f40Pm8JTFyM2mqxkG6ngkHO11f/lg==++ansi-styles@^3.2.0:+  version "3.2.1"+  resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-3.2.1.tgz#41fbb20243e50b12be0f04b8dedbf07520ce841d"+  integrity sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==+  dependencies:+    color-convert "^1.9.0"++ansi-styles@^4.0.0:+  version "4.2.1"+  resolved "https://registry.yarnpkg.com/ansi-styles/-/ansi-styles-4.2.1.tgz#90ae75c424d008d2624c5bf29ead3177ebfcf359"+  integrity sha512-9VGjrMsG1vePxcSweQsN20KY/c4zN0h9fLjqAbwbPfahM3t+NL+M9HC8xeXG2I8pX5NoamTGNuomEUFI7fcUjA==+  dependencies:+    "@types/color-name" "^1.1.1"+    color-convert "^2.0.1"++archiver-utils@^2.1.0:+  version "2.1.0"+  resolved "https://registry.yarnpkg.com/archiver-utils/-/archiver-utils-2.1.0.tgz#e8a460e94b693c3e3da182a098ca6285ba9249e2"+  integrity sha512-bEL/yUb/fNNiNTuUz979Z0Yg5L+LzLxGJz8x79lYmR54fmTIb6ob/hNQgkQnIUDWIFjZVQwl9Xs356I6BAMHfw==+  dependencies:+    glob "^7.1.4"+    graceful-fs "^4.2.0"+    lazystream "^1.0.0"+    lodash.defaults "^4.2.0"+    lodash.difference "^4.5.0"+    lodash.flatten "^4.4.0"+    lodash.isplainobject "^4.0.6"+    lodash.union "^4.6.0"+    normalize-path "^3.0.0"+    readable-stream "^2.0.0"++archiver@^4.0.1:+  version "4.0.1"+  resolved "https://registry.yarnpkg.com/archiver/-/archiver-4.0.1.tgz#3f722b121777e361ca9fad374ecda38e77e63c7f"+  integrity sha512-/YV1pU4Nhpf/rJArM23W6GTUjT0l++VbjykrCRua1TSXrn+yM8Qs7XvtwSiRse0iCe49EPNf7ktXnPsWuSb91Q==+  dependencies:+    archiver-utils "^2.1.0"+    async "^2.6.3"+    buffer-crc32 "^0.2.1"+    glob "^7.1.6"+    readable-stream "^3.6.0"+    tar-stream "^2.1.2"+    zip-stream "^3.0.1"++arg@^4.1.0:+  version "4.1.3"+  resolved "https://registry.yarnpkg.com/arg/-/arg-4.1.3.tgz#269fc7ad5b8e42cb63c896d5666017261c144089"+  integrity sha512-58S9QDqG0Xx27YwPSt9fJxivjYl432YCwfDMfZ+71RAqUrZef7LrKQZ3LHLOwCS4FLNBplP533Zx895SeOCHvA==++ast-types@0.x.x:+  version "0.13.3"+  resolved "https://registry.yarnpkg.com/ast-types/-/ast-types-0.13.3.tgz#50da3f28d17bdbc7969a3a2d83a0e4a72ae755a7"+  integrity sha512-XTZ7xGML849LkQP86sWdQzfhwbt3YwIO6MqbX9mUNYY98VKaaVZP7YNNm70IpwecbkkxmfC5IYAzOQ/2p29zRA==++astral-regex@^1.0.0:+  version "1.0.0"+  resolved "https://registry.yarnpkg.com/astral-regex/-/astral-regex-1.0.0.tgz#6c8c3fb827dd43ee3918f27b82782ab7658a6fd9"+  integrity sha512-+Ryf6g3BKoRc7jfp7ad8tM4TtMiaWvbF/1/sQcZPkkS7ag3D5nMBCe2UfOTONtAkaG0tO0ij3C5Lwmf1EiyjHg==++async@^2.6.3:+  version "2.6.3"+  resolved "https://registry.yarnpkg.com/async/-/async-2.6.3.tgz#d72625e2344a3656e3a3ad4fa749fa83299d82ff"+  integrity sha512-zflvls11DCy+dQWzTW2dzuilv8Z5X/pjfmZOWba6TNIVDm+2UDaJmXSOXlasHKfNBs8oo3M0aT50fDEWfKZjXg==+  dependencies:+    lodash "^4.17.14"

I am getting an github security alert about lodash vuln (<4.17.19).

Presumably I can update to ^4.17.19 ... but could we get away removing yarn.lock entirely? (or is it important to commit it?)

turlockmike

comment created time in 24 days

IssuesEvent

created taghayd/deno-udd

tag0.3.0

Update Deno Dependencies - update dependency urls to their latest published versions

created time in a month

release hayd/deno-udd

0.3.0

released time in a month

PR merged hayd/deno-udd

Bump deno version to 1.2.0
+5 -5

0 comment

3 changed files

hayd

pr closed time in a month

delete branch hayd/deno-udd

delete branch : 1.2.0

delete time in a month

push eventhayd/deno-udd

Andy Hayden

commit sha f28d141b60220c4fcf262fb6ca243f64445cec44

Bump deno version to 1.2.0

view details

Andy Hayden

commit sha 3c5870cb28d175e7720ca4ad9189c92ba20aff50

Merge pull request #19 from hayd/1.2.0 Bump deno version to 1.2.0

view details

push time in a month

PR opened hayd/deno-udd

Bump deno version to 1.2.0
+5 -5

0 comment

3 changed files

pr created time in a month

push eventhayd/deno-udd

Andy Hayden

commit sha f28d141b60220c4fcf262fb6ca243f64445cec44

Bump deno version to 1.2.0

view details

push time in a month

create barnchhayd/deno-udd

branch : 1.2.0

created branch time in a month

issue commenthayd/deno-zip

Cannot work on Deno 1.2.0

Thanks!

horihiro

comment created time in a month

created taghayd/deno-zip

tag0.7.0

A JSZip wrapper for handling zipfiles in deno

created time in a month

release hayd/deno-zip

0.7.0

released time in a month

push eventhayd/deno-zip

Andy Hayden

commit sha 5e0f46a3a73a64c4af6c155d83265e32ed563edd

Bump deno version to 1.2.0

view details

Andy Hayden

commit sha 5ec785ab27f85ca708785f5ed83fbedcfbe93957

Merge pull request #19 from hayd/1.2.0 Bump deno version to 1.2.0

view details

push time in a month

delete branch hayd/deno-zip

delete branch : 1.2.0

delete time in a month

PR merged hayd/deno-zip

Bump deno version to 1.2.0

Fixes #18.

+6 -6

0 comment

3 changed files

hayd

pr closed time in a month

issue closedhayd/deno-zip

Cannot work on Deno 1.2.0

It seems this is due to std's version which is pinned at 0.57.0 (0.54.0 in test.ts).

closed time in a month

horihiro

PR opened hayd/deno-zip

Bump deno version to 1.2.0

Fixes #18.

+6 -6

0 comment

3 changed files

pr created time in a month

push eventhayd/deno-zip

Andy Hayden

commit sha e1398666c282cf94a1bc9b23aa15458c95727309

Update deno to 1.1.0 and std to 0.57.0

view details

Andy Hayden

commit sha 5e0f46a3a73a64c4af6c155d83265e32ed563edd

Bump deno version to 1.2.0

view details

push time in a month

create barnchhayd/deno-zip

branch : 1.2.0

created branch time in a month

issue commenthayd/deno-docker

how about add this image?

Happy to accept a PR.

Unfortunately it doesn't seem to be as simple as adding the binary (perhaps another base image would will work - I ran into error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory). It may require a musl binary (see #5).

mrchypark

comment created time in a month

pull request commentdeno-postgres/deno-postgres

Add support for unix domain sockets

Great, thanks! One thing I am a little concerned about is running the tests requiring --unstable, it would be nice to be able to test the lib works without --unstable still (so nothing in --unstable slips into the main logic).

wilmveel

comment created time in a month

Pull request review commentdeno-postgres/deno-postgres

Add support for unix domain sockets

 function withNotAllowedEnv(fn: () => void) {  test("dsnStyleParameters", function () {   const p = createParams(-    "postgres://some_user@some_host:10101/deno_postgres",+    "postgres://some_user@some-host:10101/deno_postgres",

so the underscore in hostname is not valid?

wilmveel

comment created time in a month

Pull request review commentdeno-postgres/deno-postgres

Add support for unix domain sockets

-import { parseDsn } from "./utils.ts";+import { parseDsn, validHostname } from "./utils.ts";+import validate = WebAssembly.validate;

unused?

wilmveel

comment created time in a month

push eventdeno-postgres/deno-postgres

Edward Bebbington

commit sha 03dbafa983c3eb86a23e9a6514f18b4b2d2c2ac5

[update-docs] Document query result interface

view details

Edward Bebbington

commit sha ffa2e82b5d29a82a89f904b9d5876876cb162ab3

[update-docs] Document pools for connection management

view details

Edward Bebbington

commit sha 1d625184ee3e2d8f37feed26d1fc1a88dc2fb1b9

[update-docs] Update Pool documentation

view details

Andy Hayden

commit sha 28249fbec10f7f1581f405a5a5b4b105a838629b

Merge pull request #150 from ebebbington/update-docs [update-docs] Add further documentation

view details

push time in a month

PR merged deno-postgres/deno-postgres

[update-docs] Add further documentation

Fixes #145

Fixes #147

Adds documentation on the returned type for a query. This fixes issues for people who use deno lint (it throws a lot of errors when executing on result or client)

+54 -0

0 comment

1 changed file

ebebbington

pr closed time in a month

issue closeddeno-postgres/deno-postgres

Connection Management Best Practices

What are the best practices for managing our connections to the database? I'm unsure of how to manage these properly and the readme doesn't really provide much guidance on this. Currently I'm opening a connection, executing my query and then closing the connection. Is there a recommended way to handle eliminating this code duplication?

closed time in a month

FraserHamilton

issue closeddeno-postgres/deno-postgres

DB Result Interface

Add an exported interface that we can assign as a type to the returned data of .query(). For example:

// no interface, separate. project
const dbResult = await client.query(...)
if (dbResult.rowCount < 1) { // "TS Error: Object is possibly undefined"
  return false
}

// With interface
import { IQueryResult } from "https://deno.land/x/postgres@v0.4.2/query.ts";
const dbResult: IQueryResult = await client.query(...)
if (dbResult.rowCount < 1) { // passes
  return false
}

closed time in a month

ebebbington

Pull request review commentdeno-postgres/deno-postgres

[update-docs] Add further documentation

 async function main() { main(); ``` +## Connection Management++You are free to create your 'clients' like so:++```typescript+const client = new Client({+  ...+})+await client.connect()+```++But for stronger management and scalability, you can use **pools**:+```typescript+import { Pool } from "https://deno.land/x/postgres@v0.4.0/mod.ts";+import { PoolClient } from "https://deno.land/x/postgres@v0.4.0/client.ts";++const POOL_CONNECTIONS = 50;+const dbPool = new Pool({+  user: "user",+  password: "password",+  database: "database",+  hostname: "hostname",+  port: 5432,+}, POOL_CONNECTIONS);++function runQuery (query: string) {+  const client: PoolClient = await dbPool.connect();+  const dbResult = await client.query(query);+  client.release();+  return dbResult+}++runQuery("SELECT * FROM users;");+runQuery("SELECT * FROM users WHERE id = '1';");+```++This improves performance, as creating a whole new connection for each query can be an expensive operation.+With pools, you can keep the connections open to be re-used when requested (`const client = dbPool.connect()`). So one of the active connections will be used instead  of creating a new one.++The number of pools is up to you, but 50 is generally a good number, but this can differ based on how active your application is.

ha! I just looked at a few applications and see 200 - so maybe I was confused (though I've no idea how well deno handles that many open). I'd probably say "many" applications (or even "most") rather than "small".

Will merge anyway. One thing I like to use sometimes is to have multiple query pools - that way longer-running queries can be put into a separate pool (and not slow down queries which are important to be fast).

ebebbington

comment created time in a month

issue commentdeno-postgres/deno-postgres

Insert should return lastidinserted.

You kinda want to do RETURNING MAX(id), count(1) (so as to avoid sending all the data back, or doing two queries) but that isn't valid...

aggregate functions are not allowed in RETURNING

tksilicon

comment created time in a month

Pull request review commentdeno-postgres/deno-postgres

[update-docs] Add further documentation

 async function main() { main(); ``` +## Connection Management++You are free to create your 'clients' like so:++```typescript+const client = new Client({+  ...+})+await client.connect()+```++But for stronger management and scalability, you can use **pools**:+```typescript+import { Pool } from "https://deno.land/x/postgres@v0.4.0/mod.ts";+import { PoolClient } from "https://deno.land/x/postgres@v0.4.0/client.ts";++const POOL_CONNECTIONS = 50;+const dbPool = new Pool({+  user: "user",+  password: "password",+  database: "database",+  hostname: "hostname",+  port: 5432,+}, POOL_CONNECTIONS);++function runQuery (query: string) {+  const client: PoolClient = await dbPool.connect();+  const dbResult = await client.query(query);+  client.release();+  return dbResult+}++runQuery("SELECT * FROM users;");+runQuery("SELECT * FROM users WHERE id = '1';");+```++This improves performance, as creating a whole new connection for each query can be an expensive operation.+With pools, you can keep the connections open to be re-used when requested (`const client = dbPool.connect()`). So one of the active connections will be used instead  of creating a new one.++The number of pools is up to you, but 50 is generally a good number, but this can differ based on how active your application is.

where did you see 50 as being a good number? I thought I had seen 20 be recommended (somewhere)... 😄

Overall this seems good change 👍

ebebbington

comment created time in a month

more