Raynos ( Jake Verbaten )

commit sha 432158677d1ae2f143158c33e548d3182a310804

Update README.md

Elaborate on difference to eslint-config-standard-with-typescript

push time in 3 days

issue closedRaynos/eslint-config-tsdocstandard

Would be great for users and contributors to have an in depth comparison to the eslint-config-standard-with-typescript project, especially when it comes to the typescript related standardjs rules

closed time in 3 days

voxpelli

issue commentRaynos/eslint-config-tsdocstandard

Elaborate on difference to eslint-config-standard-with-typescript

Updated README.

voxpelli

comment created time in 3 days

push eventRaynos/eslint-config-tsdocstandard

commit sha 9cb74efeb59745e22e0d9e89253b3af552a3a4c1

Update README.md

Upgrade typescript eslint to latest version.

push time in 3 days

pull request commentstandard/standard

Upgrade to ESLint 7

I’m not comfortable merging these PRs as is.

Would it be ok to create a temporary git repo standard7 and eslint-config-standard7 ?

I can merge all these PRs in there and then publish new npm packages standard7 / eslint-config-standard7 .

The community can play with these packages and once all the bugs are worked out everything can be merged into standard version 15

Cc @linusu @feross @voxpelli

LinusU

comment created time in 3 days

issue openedRaynos/tsdocstandard

created time in 3 days

issue commentRaynos/tsdocstandard

Detect missing tsconfig.json and scaffold the basics.

The way this would look today actually would be to detect no tsconfig.json or jsconfig.json and to scaffold the correct files.

Copy _types/base-tsconfig.json into the current workding dir ( https://github.com/optoolco/fake-aws/blob/master/_types/base-tsconfig.json )
Drop a jsconfig.json ( https://github.com/optoolco/fake-aws/blob/master/jsconfig.json ).

For the jsconfig the following should be an ok starting point

{
  "extends": "./_types/base-tsconfig.json",
  "compilerOptions": {
    "baseUrl": "./",
    "paths": {
      "*" : ["./_types/*"]
    }
  },
  "include": [
    "*.js",
    "test/*.js",
    "_types/**/*.d.ts"
  ]
}

Raynos

comment created time in 3 days

push eventRaynos/tsdocstandard

commit sha fac22ee0a1b1ac4f8116915cedf646151a3b1f9c

Update README.md

Support for not directly inheriting from `HTMLElement`

push time in 3 days

issue openedrunem/web-component-analyzer

Our web components do not extends HTMLElement directly in their implementation

Instead they extends Tonic and tonic extends HTMLElement

I added @element ${name} to one of my web components and the analyzer was able to find it.

Would it be possible for the analyzer to be able to find that it does inherit from HTMLElement via base class ?

Alternatively I'm happy to configure the analyzer with wca analyzer --super Tonic as a hint.

created time in 3 days

push eventoptoolco/tonic

commit sha 1c78c7c5c15ab5787c50c022cde40213b0faf526

update API

Add beforeAll(), afterAll(), beforeEach(), afterEach()

push time in 3 days

PR opened optoolco/tonic

src: Add dispatch method

Small ergonomic improvement for dispatching a custom event on a Tonic component.

A parent component can use this.addEventListener(eventName, this) to listen for the event if it implements a method thats the same as eventName.

This brings up the cloc count from 325 => 329.

r: @heapwolf

+5 -0

1 commit in optoolco/tonic/tree/dispatch-method optoolco/tonic/tree/master

0 comment

1 changed file

pr created time in 3 days

create barnchoptoolco/tonic

branch : dispatch-method

created branch time in 3 days

issue commentsubstack/tape

do you mean technically or politically (or both)?

Last time I touched something related to how subtests work I broke someone else's workflow. Looking at the open issues, i suspect there's still unresolved sharp edges related to ordering edge cases.

My tape-harness library is sufficiently opinionated and works very well for my personal testing / tape workflows and doesn't break anyone else's code because it has 70 downloads instead of 500,000 downloads.

ryanblock

comment created time in 4 days

created tagoptoolco/components

tagv12.1.2

Example Components (Built with Tonic, the Web Components Framework)

created time in 4 days

push eventoptoolco/components

commit sha 17c85d9183098682ada2caafbcf7c5b3503c9ed9

npmignore: Keep the dist dir

commit sha ec091d776b032fe088b8215cff1b841121b9f36f

12.1.2

push time in 4 days

push eventoptoolco/components

commit sha 2fb5c1bf6719586ed6c101d2fae28da84702f062

regen build

commit sha 7ed4433e4b97672468e2cdd325357fa6f15a9aa0

12.1.1

push time in 4 days

created tagoptoolco/components

tagv12.1.1

Example Components (Built with Tonic, the Web Components Framework)

created time in 4 days

created tagoptoolco/components

tagv12.1.0

Example Components (Built with Tonic, the Web Components Framework)

created time in 4 days

push eventoptoolco/components

commit sha c19553d54bcf5421b92cc96647e9997e63a486da

12.1.0

Add beforeAll(), afterAll(), beforeEach(), afterEach()

push time in 4 days

delete branch optoolco/components

delete branch : fix-input

delete time in 4 days

PR merged optoolco/components

tonic-input was not working in wizard.

When the component reRendered it defaulted to empty string even though there was text in the input previously.

This is because the parent's parent reRendered and the _modified is false as its a new DOM element.

+11 -9

3 commit in optoolco/components/tree/fix-input optoolco/components/tree/master

0 comment

3 changed files

Raynos

pr closed time in 4 days

PR opened optoolco/components

tonic-input was not working in wizard.

When the component reRendered it defaulted to empty string even though there was text in the input previously.

This is because the parent's parent reRendered and the _modified is false as its a new DOM element.

+11 -9

3 commit in optoolco/components/tree/fix-input optoolco/components/tree/master

0 comment

3 changed files

pr created time in 4 days

create barnchoptoolco/components

branch : fix-input

created branch time in 4 days

issue commentsubstack/tape

Adding new features to tape is harder then authoring a new dependency. We added async function support last year and that took a while to actually get everyone on board & released.

That being said I'm in favor of merging tape-harness into tape and exposing it as const createHarness = require('tape/harness') ( note it doesn't implement the beforeEach or afterEach API but achieves a similar result ).

ryanblock

comment created time in 4 days

issue commentsubstack/tape

Add beforeAll(), afterAll(), beforeEach(), afterEach()

You make a valid point that using the first & last test as beforeAll & afterAll does not play well with test.only(). Opening a seperate issue that adds an always option like

test('setup', { always: true }, (t) => {
  ...
})

test('one')
test('two')
test.only('three')

test('teardown', { always: true }, (t) => {

})

So that the setup & teardown always run even if test.only is called.

This property could be called something else like ignoreOnly.

ryanblock

comment created time in 4 days

issue commentsubstack/tape

Add beforeAll(), afterAll(), beforeEach(), afterEach()

beforeAll is the first test statement in a file. afterAll is the last test statement in a file.

The use case of beforeEach & afterEach is better handled with a userland module like

https://www.npmjs.com/package/redtape
https://www.npmjs.com/package/tape-harness

Duplicate of https://github.com/substack/tape/issues/59

ryanblock

comment created time in 4 days

issue commentmicrosoft/TypeScript

Cannot annotate a field in constructor as null using jsdoc @type

Could we reduce confusion by warnings that annotating somethings it as not supported ?

/** @type {null} */ <= error here. null in @type not supported
this.foo = null

Some form of warning that using null with @type is treated the same as any and is thus not recommended or not useful.

Raynos

comment created time in 5 days

issue commentmicrosoft/TypeScript

Cannot annotate a field in constructor as null using jsdoc @type

@Raynos can you explain what you were using it for?

This workflow is for converting an existing JavaScript class into a JSDoc --checkJS // @ts-check class.

I have a large existing class I want to introduce type safety to.
The constructor is the first method in the class block
A field is null in the constructor but is then updated to be some concrete object in some asynchronous method further down in the class
I want to add a type annotation to every this field in the constructor so I can get explicit type checking
Added @type {null} is valid for the constructor to type check and remove the red errors.
There should now be an error in some other method further down the class where assigning a concrete object to null is a type error
I can find that error and then update the type annotation in the constructor to be @type {null | MyThing}

I don't need a @type {null} but its a useful temporary annotation to remove red errors linearly in my text editor / tsc CLI as I'm going through a untyped file.

Raynos

comment created time in 5 days

issue closedbrowserify/browserify

Publishing new version to npm & help.

Hi browserify folks,

I see that the latest code in master has not been published to npm yet.

I'd love to help out with maintenance for browserify & watchify. I'm currently the browserify github org but don't have npm publish access.

Could you run the following ?

npm owner add raynos browserify
npm owner add raynos watchify

cc @goto-bus-stop @ljharb @feross

closed time in 9 days

Raynos

issue commentbrowserify/browserify

Publishing new version to npm & help.

Thanks for publishing v17 !

Raynos

comment created time in 9 days

issue openedbrowserify/browserify

Publishing new version to npm & help.

Hi browserify folks,

I see that the latest code in master has not been published to npm yet.

I'd love to help out with maintenance for browserify & watchify. I'm currently the browserify github org but don't have npm publish access.

Could you run the following ?

npm owner add raynos browserify
npm owner add raynos watchify

cc @goto-bus-stop @ljharb @feross

created time in 10 days

issue commentbrowserify/browserify

promisify is not a function - util dependency version

I think this is fixed on master but not published to npm.

acailly

comment created time in 10 days

push eventRaynos/watchify

commit sha 52fce795744d8b272955d9cda143366a981e38d0

use raynos-browserify

commit sha 4afabc4fa995df5e7fd26890b9da54d65886e099

rename damn thing

commit sha 69f93ab93d741b057ac3b3181d88abe04cf0807f

3.11.1-raynos-patch1

push time in 10 days

fork Raynos/watchify

watch mode for browserify builds

browserify/watchify Raynos/watchify

fork in 10 days

created tagoptoolco/fake-aws

tagv0.1.3

This package contains a set of fake AWS servers that can be used as part of your integration test suite.

created time in 11 days

push eventoptoolco/fake-aws

commit sha e81622945e5a2dcc220700723b96f5c07833c7ed

rename package

commit sha 661f27ac39ca76bcc75ce5f038e3d3f69d21be70

0.1.3

push time in 11 days

push eventoptoolco/fake-aws

commit sha c55c23267da9442a77e2b548594efb1803c1f3f1

0.1.2

push time in 11 days

created tagoptoolco/fake-aws

tagv0.1.2

This package contains a set of fake AWS servers that can be used as part of your integration test suite.

created time in 11 days

push eventRaynos/fake-s3

commit sha d4561ffc060d7abff0b1a46c257531b273ceb42f

delete unused dep

Import more packages from raynos

push time in 11 days

issue openedoptoolco/fake-aws

Three packages were imported into this repo.

There are more available to copy over if needed

https://github.com/Raynos/fake-sqs
https://github.com/Raynos/fake-kms
https://github.com/Raynos/fake-ses

There's also https://github.com/Raynos/fake-api-gateway-lambda which is not related to aws-sdk but is used to emulate an API Gateway with lambdas in it.

created time in 11 days

push eventoptoolco/fake-aws

commit sha f11d22ef88f59f092509d8de15d0cca233c44f88

add cloudwatchlogs

push time in 11 days

push eventoptoolco/fake-aws

commit sha dc27d23a294093ecc1781dc236b75159395d47f6

add lambda package

push time in 11 days

push eventoptoolco/fake-aws

commit sha fc152dcadfcef96fb18b9678336998477778aaac

add s3 package

commit sha 617bde20d27e53eada294b4cf32e6eb2973861c5

add README

push time in 11 days

create barnchoptoolco/fake-aws

branch : master

created branch time in 11 days

created repositoryoptoolco/fake-aws

created time in 11 days

created tagRaynos/fake-s3

tagv4.0.0

a fake s3 server for testing purposes.

created time in 11 days

push eventRaynos/fake-s3

commit sha 3c42f9cc84b7d69d7d7e20de0e0f62a7c7fd870f

4.0.0

push time in 11 days

push eventRaynos/tsdocstandard

commit sha 18468167093ca0a23d738b2ce09f42887071b10c

Update README.md

push time in 11 days

delete branch Raynos/fake-s3

delete branch : jsdoc

delete time in 11 days

push eventRaynos/fake-s3

commit sha 3440ac7f54f8839bd569ebf5c6b18d04f1cd9313

simplify package.json

commit sha 32452d200b0932b55759d51e351e0afe2bfcff43

config files

commit sha b6c4c44f7d45863f4b9f4c7fe9b7498c08d15eac

update package.json

commit sha 33eaf6d5a3124679c450eead5455fe8871f4f5bd

enable checkJs

commit sha 08194149a44510e47ef9ccb4455e1b27b2ae1dfb

wip

commit sha 282fa39134611857759c1b6a81ccc5cf5d75ccd3

wip

commit sha 53d925a1f5174db11e5a55fcd8c1ebdd8a819cea

update types

commit sha 21aeb2d4efc929575a4614ed08b8e93fb2caf100

update tests

commit sha dd111e26d187b06eb809086b279cf2ed492577e1

pass lint

commit sha 04b3bf8e9383f22250ec188e46bf14eb2fc608a5

add new linter

commit sha 16f240be3db3c350feb697aab1f70361ce3f04fd

update code to fix lints

commit sha 99a1a2dce09b09bc09a60afe112d5acb2a925cf3

pkg: Add type-coverage

commit sha 7547b72dd155303b1b2d0cd6b8877608e6095302

add annotations to get 100% type coverage

commit sha 7f33a7443ec8e399934178ee566994cc0d881009

Merge pull request #3 from Raynos/jsdoc Add JSDoc annotations + TypeScript

push time in 11 days

PR merged Raynos/fake-s3

Add JSDoc annotations + TypeScript

This adds jsconfig.json and JSDoc annotations to the source code.

We verify if the JSDoc matches the implementation by using typescript & tsdocstandard & type-coverage.

+842 -287

13 commit in Raynos/fake-s3/tree/jsdoc Raynos/fake-s3/tree/master

0 comment

11 changed files

Raynos

pr closed time in 11 days

PR opened Raynos/fake-s3

Add JSDoc annotations + TypeScript

This adds jsconfig.json and JSDoc annotations to the source code.

We verify if the JSDoc matches the implementation by using typescript & tsdocstandard & type-coverage.

+842 -287

13 commit in Raynos/fake-s3/tree/jsdoc Raynos/fake-s3/tree/master

0 comment

11 changed files

pr created time in 11 days

push eventRaynos/fake-s3

commit sha 04b3bf8e9383f22250ec188e46bf14eb2fc608a5

add new linter

commit sha 16f240be3db3c350feb697aab1f70361ce3f04fd

update code to fix lints

commit sha 99a1a2dce09b09bc09a60afe112d5acb2a925cf3

pkg: Add type-coverage

commit sha 7547b72dd155303b1b2d0cd6b8877608e6095302

add annotations to get 100% type coverage

Go to definition broken by existance of tsconfig.json in JavaScript project.

push time in 11 days

issue commentmicrosoft/TypeScript

maxNodeModuleJsDepth

This is an interesting point. I've noticed the consequence of using jsconfig.json in that I need to set maxNodeModuleJsDepth manually with the cli like tsc -p jsconfig.json --maxNodeModuleJsDepth 0

I do want this max depth 0 behavior when running the compiler to check my code, but i want >0 max depth when using go to definition on a require statement in a javascript file.

Raynos

comment created time in 11 days

issue commentmicrosoft/TypeScript

Go to definition broken by existance of tsconfig.json in JavaScript project.

my only concern is that for a TypeScript user, that “no definition found” message can be a useful cue to install @types/uuid

This makes sense to me if I'm editing a .ts typescript file and I'm using the typescript import syntax.

It was not clear from my example but it's actually a .js file and I'm using require because my version of node does not support import / export.

Raynos

comment created time in 11 days

issue openedmicrosoft/TypeScript

Cannot annotate a field in constructor as null using jsdoc @type

<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a bug, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:

Search: https://github.com/Microsoft/TypeScript/search?type=Issues
Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the entire template below. -->

TypeScript Version: 4.0.2

Search Terms: jsdoc null type implicit any

Code

class Foo {
    constructor () {
        /** @type {number} */
        this.bar = 42

        /** @type {null} */
        this.foo = null
    }
}

Expected behavior:

Expected to have a class with two fields, bar of type number & foo of type null

I don't know why it doesn't understand null; using string | null works fine.

Actual behavior: Member 'foo' implicitly has an 'any' type.

Playground Link: https://www.typescriptlang.org/play?useJavaScript=true#code/MYGwhgzhAEBiD29oG8BQ0PWPAdhALgE4Cuw+8h0AFAJQrqaMD0AVC9AAL4CeADgKYocxALYAjfoQC+0FkwaMM+ABYBLCADoxYSgF5oAFgBMqBYtbsufQcmEgQMuWcYr1GgGaJo+uyDNTUKSA

Related Issues:

created time in 12 days

created tagRaynos/tsdocstandard

tagv15.7.1

Standard but also use TypeScript on JS files with jsdoc.

created time in 12 days

push eventRaynos/tsdocstandard

commit sha ab86627356ae234e338e6c2f28c7d40562b95c6c

update config

commit sha dc6e5f11449da8010bcf3c98e540d1ff7c5c5525

15.7.1

push time in 12 days

push eventRaynos/eslint-config-tsdocstandard

commit sha 0aa9746e3450eb2e2235bfe86c5e45d28ad058c7

allow constructor only class

commit sha 97cc391617781c22290f8d74bf179f635673d8d6

16.2.5

push time in 12 days

created tagRaynos/eslint-config-tsdocstandard

tagv16.2.5

eslint sharable config for tsdocstandard

created time in 12 days

push eventRaynos/tsdocstandard

commit sha af77a437e6f03dc886b83405b86567bc5532d610

support jsconfig.json

commit sha 0c97aa4f96d79050bab574fe7c8dc06cf5c7415c

15.7.0

push time in 12 days

created tagRaynos/tsdocstandard

tagv15.7.0

Standard but also use TypeScript on JS files with jsdoc.

created time in 12 days

push eventRaynos/fake-s3

commit sha 53d925a1f5174db11e5a55fcd8c1ebdd8a819cea

update types

commit sha 21aeb2d4efc929575a4614ed08b8e93fb2caf100

update tests

commit sha dd111e26d187b06eb809086b279cf2ed492577e1

pass lint

Do not type check .js files in referenced node_modules under `--checkJs` and `--maxNodeModuleJsDepth` > 0

push time in 12 days

issue commentmicrosoft/TypeScript

A reproduction can be found on this commit for this git repo ( https://github.com/Raynos/fake-s3/commit/282fa39134611857759c1b6a81ccc5cf5d75ccd3 ).

Running npm run tsc outputs 400 typescript errors for node_modules/* but zero errors for my source code ( index.js with jsdoc ).

mhegazy

comment created time in 12 days

push eventRaynos/fake-s3

commit sha 282fa39134611857759c1b6a81ccc5cf5d75ccd3

wip

Do not type check .js files in referenced node_modules under `--checkJs` and `--maxNodeModuleJsDepth` > 0

push time in 12 days

create barnchRaynos/fake-s3

branch : jsdoc

created branch time in 12 days

issue commentmicrosoft/TypeScript

I've run into this issue and thought I could fix it with adding exclude to my jsconfig.json

+  "exclude": ["node_modules"]

I was suprised to find that tsc -p jsconfig.json still checkes node_modules even though exclude is explicitely set in the jsconfig

mhegazy

comment created time in 12 days

issue commentmicrosoft/TypeScript

Go to definition broken by existance of tsconfig.json in JavaScript project.

I renamed the tsconfig.json to jsconfig.json and now go to definition works again ...

I guess it's my fault for not using jsconfig.json ...

Raynos

comment created time in 12 days

issue openedmicrosoft/TypeScript

Go to definition broken by existance of tsconfig.json in JavaScript project.

<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a bug, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:

Search: https://github.com/Microsoft/TypeScript/search?type=Issues
Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the entire template below. -->

TypeScript Version: 4.0.2

Search Terms: go to definition javascript

Code

'use strict'

// javascript file.
const uuid = require('uuid')

Expected behavior:

When I hit Go to definition with F12 on uuid it goes to the source code.

working-go-to-def

This works fine for JavaScript because tsconfig.json does not exist.

Actual behavior:

When I hit Go to definition with F12 it does not do anything useful.

broken-go-todef

This is because a tsconfig.json file exists in my JavaScript project.

Playground Link:

Related Issues:

created time in 12 days

issue commentmicrosoft/vscode

Support syntax highlight of typescript expressions in multiline jsdoc comments

The same holds true for multi line type definitions

Raynos

comment created time in 12 days

issue openedmicrosoft/vscode

Support syntax highlight of typescript expressions in multiline jsdoc comments

Currently jsdoc annotations that include typescript expressions for javascript with // @ts-check do not support the right colors when spread out over multiple lines.

The second parameter buckets is spread out over multiple lines and has the comment color instead of the type expression color.

created time in 12 days

push eventoptoolco/components

commit sha ae9802c75a73a4f55dbe823474686f2be55bee48

Update MIGRATION.md

push time in 20 days

PullRequestReviewEvent

pull request commentoptoolco/components

input state selection

Please get CI passing.

heapwolf

comment created time in 21 days

delete branch optoolco/components

delete branch : improve-dialog

delete time in 21 days

startedoptoolco/async-level

started time in 24 days

create barnchoptoolco/components

branch : improve-dialog

created branch time in a month

push eventoptoolco/components

commit sha d6621f314aa37c96518fd92c94f5004d4c04d783

tabs: Do not dispatch event synchronously Only dispatch the tabvisible / tabhidden change events on user interaction.

push time in a month

delete branch optoolco/components

delete branch : improve-dialog

delete time in a month

PullRequestReviewEvent

push eventRaynos/tape-harness

commit sha 5469fe06587cc2f8071a9d9b2f89b23954a41c25

cleanup project

commit sha 7e9bcf3a491ed19b33e54fd27ae637607edf8def

delete dead files

commit sha d70a5636a4457d0f5322c5b8410628acc1f257c3

cleanup package.json

commit sha 3b7abda96aac6e722c5deb8248a047eb4480d92a

fix lint

commit sha 338575926424207d4939643de4e7309dbc01a273

cleanup test suite

commit sha 3ec5eb00c56b7f4c0a5c22b95c1bd12326f8a0f5

update pkg

commit sha a0453ef23645f7129b4df2f686cc0307bcfd4d47

add tsconfig & external types

commit sha 331b2b68c8ee81ee24d1313e369d19dfa4f211a9

rewrite + jsdoc annotations

commit sha 6e38ad02f1f12faace6dfb669134e789828a9613

5.0.0

Support `assert.plan` method

push time in a month

created tagRaynos/tape-harness

tagv5.0.0

A helper to run integration tests against an application

created time in a month

PR closed Raynos/tape-harness

Support `assert.plan` method

Tape has a plan method we can use as an alternative to calling end. However, this was not supported by tape-cluster and unit tests would hang.

In this PR, instead of overwriting the assert.end function, we listen for the assert.end event then call the asyncEnd method. This allows us to use the assert.plan method as well as assert.end.

+14 -4

1 commit in nickpeihl/tape-cluster/tree/plan-fix Raynos/tape-harness/tree/master

1 comment

2 changed files

nickpeihl

pr closed time in a month

pull request commentRaynos/tape-harness

In the latests version of tape-harness we monkey patch t.plan to let the user know that t.plan() is not supported.

nickpeihl

comment created time in a month

PR closed Raynos/tape-harness

Bump acorn from 6.1.1 to 6.4.1 dependencies

Bumps acorn from 6.1.1 to 6.4.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/acornjs/acorn/commit/9a2e9b6678e243d66846b91179d650d28453e70c"><code>9a2e9b6</code></a> Mark version 6.4.1</li> <li><a href="https://github.com/acornjs/acorn/commit/90a9548ea0ce351b54f956e2c4ed27cca9631284"><code>90a9548</code></a> More rigorously check surrogate pairs in regexp validator</li> <li><a href="https://github.com/acornjs/acorn/commit/df0cf1a3e2b1a51a26c14984dc0f5412b7151b10"><code>df0cf1a</code></a> Mark version 6.4.0</li> <li><a href="https://github.com/acornjs/acorn/commit/53034126864b492da4e278628bb972cb2a9313d4"><code>5303412</code></a> Also export Parser via Parser.acorn</li> <li><a href="https://github.com/acornjs/acorn/commit/efe273e70123449a458157dbf578afaf109a49ab"><code>efe273e</code></a> give token types and etc to plugins</li> <li><a href="https://github.com/acornjs/acorn/commit/ac6decb94a3aa4eee99230fdaf5883dfaafe8479"><code>ac6decb</code></a> Mark version 6.3.0</li> <li><a href="https://github.com/acornjs/acorn/commit/7e9817d17639d95cc6dbacfde734a0626b2a7dea"><code>7e9817d</code></a> Allow sourceType: module even with ecmaVersion < 6</li> <li><a href="https://github.com/acornjs/acorn/commit/e2b8cc087386eccc2ad6fd4a02b4257833557cb3"><code>e2b8cc0</code></a> Fix broken parsing of new expressions when allowReserved=="never"</li> <li><a href="https://github.com/acornjs/acorn/commit/1555c528855b10320ce98b4154906d7898c92990"><code>1555c52</code></a> Update acorn.d.ts</li> <li><a href="https://github.com/acornjs/acorn/commit/77c20fa2c2f490e646b67e6a0ff7e75fb54ab6c8"><code>77c20fa</code></a> Mark version 6.2.1</li> <li>Additional commits viewable in <a href="https://github.com/acornjs/acorn/compare/6.1.1...6.4.1">compare view</a></li> </ul> </details> <br />

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>

+18 -3

1 commit in Raynos/tape-harness/tree/dependabot/npm_and_yarn/acorn-6.4.1 Raynos/tape-harness/tree/master

0 comment

1 changed file

dependabot[bot]

pr closed time in a month

push eventoptoolco/async-level

commit sha f518a1a2af72d763063cc4abd91047bd512eaa30

Update README.md

Change prebuild infrastructure to use prebuildify

push time in a month

issue commentoptoolco/tonic

Create example apps

Svelte js has a hacker news example. This is a good idea, probably better then todo mvc

heapwolf

comment created time in a month

issue commentVenemo/node-lmdb

Thanks kris ! I’ll take a look when I get a chance

Raynos

comment created time in a month

created tagoptoolco/append-fs-logger

tagv2.0.0

Lightweight, zero dependency logger designed mostly for electron applications.

created time in 2 months

push eventoptoolco/append-fs-logger

commit sha d20c425256dd76a7a2bcc99cbdbffcae90b2a837

2.0.0

push time in 2 months

delete branch optoolco/append-fs-logger

delete branch : remove-renderer-logger

delete time in 2 months

push eventoptoolco/append-fs-logger

commit sha 21b1c973c07b10088b17626d9b4cfc4a386ee16f

src: Remove RendererLogger. This class should not have been here. It's not related to append-fs-logger. We've moved this electron specific code to our electron-base module instead.

commit sha 054eae99b6f8a9432976719c3b37146741ae62b1

remove renderer reference in README

commit sha 96109cb695313e8e1d7fc5ce8fec97e972ec7c97

Merge pull request #3 from optoolco/remove-renderer-logger Remove RendererLogger

push time in 2 months

PR merged optoolco/append-fs-logger

Remove RendererLogger

The RendererLogger class is electron specific and should not have been in this git repo. We've moved it to our internal _electron-base module / repo instead.

+0 -228

2 commit in optoolco/append-fs-logger/tree/remove-renderer-logger optoolco/append-fs-logger/tree/master

0 comment

2 changed files

Raynos

pr closed time in 2 months

push eventoptoolco/tonic

commit sha b2f1b36a5ddb7d1039b03923fa6ebe3d2c9bbfad

update migration docs

commit sha c011bdfcc8f6d8a1841f43e1458d96c0415ae01a

Merge pull request #61 from optoolco/migrate-docs update migration docs