Description of change

Implementing the Serialize trait on the events structs so we can use them on the actor system.

Type of change

• Enhancement (a non-breaking change which adds functionality)

How the change has been tested

Actually using it on the new wallet backend.

Change checklist

• [x] I have followed the contribution guidelines for this project
• [x] I have performed a self-review of my own code
• [x] I have checked that new and existing unit tests pass locally with my changes

Description of change

Implementing the Serialize trait on the events structs so we can use them on the actor system.

Type of change

• Enhancement (a non-breaking change which adds functionality)

How the change has been tested

Actually using it on the new wallet backend.

Change checklist

• [x] I have followed the contribution guidelines for this project
• [x] I have performed a self-review of my own code
• [x] I have checked that new and existing unit tests pass locally with my changes

Description of change

Update lib code to latest bee-message refactor and use iota-core from dev (chrysalis branch was merged).

Type of change

• dependency update

How the change has been tested

Unit tests.

Change checklist

• [x] I have followed the contribution guidelines for this project
• [x] I have performed a self-review of my own code
• [x] I have checked that new and existing unit tests pass locally with my changes

Description of change

Implementing the event notification through polling.

Type of change

• Enhancement (a non-breaking change which adds functionality)

How the change has been tested

Not tested yet, will do after the Hornet tests.

Change checklist

• [x] I have followed the contribution guidelines for this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have checked that new and existing unit tests pass locally with my changes

Description of change

Renaming serialization to match the default (camelCase).

Type of change

• Enhancement (a non-breaking change which adds functionality)

Description of change

Renaming serialization to match the default (camelCase).

Type of change

• Enhancement (a non-breaking change which adds functionality)

Description of change

Changing some return types and implementing some traits to simplify the wallet actor.

Type of change

• Enhancement (a non-breaking change which adds functionality)

How the change has been tested

Unit tests, actors.rs build.

Change checklist

• [x] I have followed the contribution guidelines for this project
• [x] I have performed a self-review of my own code
• [x] I have checked that new and existing unit tests pass locally with my changes

Description of change

Fixes typo (post_messages -> post_message)

Links to any relevant issues

N/A

Type of change

• Bug fix (a non-breaking change which fixes an issue)

How the change has been tested

Builds successfully

Change checklist

• [x] I have followed the contribution guidelines for this project
• [x] I have performed a self-review of my own code
• [x] I have checked that new and existing unit tests pass locally with my changes

Yeah this was an upstream change :D

The code for the bundler is located in `[Tauri repo root]/cli/tauri-bundler`. After making your changes to the code, run `cargo install --path . --force` in the bundler directory. This will update the global `tauri-bundler` Cargo install to use your local code. Now, all of your Tauri projects will use the local code when bundling. The Cargo install needs to be run after every change.

This PR contains the following updates:

Release Notes

<details> <summary>babel/babel</summary>

v7.12.3

Compare Source

:bug: Bug Fix

• babel-helper-wrap-function, babel-plugin-proposal-async-generator-functions
  • #​12192 fix: properly wrap private class methods (@​JLHwung)
• babel-core
  • #​12200 Make loadPartialConfig's options optional (@​nicolo-ribaudo)
• babel-parser
  • #​12185 [ts] Disallow invalid type annotations in ExpressionStatements (@​existentialism)

:house: Internal

• Other
  • #​12204 chore: update test262 tests (@​JLHwung)
• babel-parser
  • #​12203 test: add test case for babel-parser: fixtures/typescript/arrow-function/destructuring-with-annotation-newline (@​Mongkii)

v7.12.1

Compare Source

:bug: Bug Fix

• babel-cli
  • #​12182 Don't force chokidar@2 to be downloaded from registry.npmjs.org (@​nicolo-ribaudo)
• babel-plugin-transform-runtime, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • #​12184 Allow importing @babel/runtime/package (@​nicolo-ribaudo)
• babel-parser
  • #​12183 Reland "Fix: check if param is assignable when parsing arrow return type annotation" (@​nicolo-ribaudo)

:house: Internal

• Other
  • #​12188 Guard against yarn-issue-1882 (@​JLHwung)
• babel-cli, babel-core, babel-generator, babel-helper-bindify-decorators, babel-helper-call-delegate, babel-helper-compilation-targets, babel-helper-create-class-features-plugin, babel-helper-create-regexp-features-plugin, babel-helper-explode-assignable-expression, babel-helper-explode-class, babel-helper-module-imports, babel-helper-remap-async-to-generator, babel-helper-skip-transparent-expression-wrappers, babel-helpers, babel-node, babel-parser, babel-plugin-external-helpers, babel-plugin-proposal-async-generator-functions, babel-plugin-proposal-class-properties, babel-plugin-proposal-class-static-block, babel-plugin-proposal-decorators, babel-plugin-proposal-do-expressions, babel-plugin-proposal-dynamic-import, babel-plugin-proposal-export-default-from, babel-plugin-proposal-export-namespace-from, babel-plugin-proposal-function-bind, babel-plugin-proposal-function-sent, babel-plugin-proposal-json-strings, babel-plugin-proposal-logical-assignment-operators, babel-plugin-proposal-nullish-coalescing-operator, babel-plugin-proposal-numeric-separator, babel-plugin-proposal-object-rest-spread, babel-plugin-proposal-optional-catch-binding, babel-plugin-proposal-optional-chaining, babel-plugin-proposal-partial-application, babel-plugin-proposal-pipeline-operator, babel-plugin-proposal-private-methods, babel-plugin-proposal-private-property-in-object, babel-plugin-proposal-throw-expressions, babel-plugin-proposal-unicode-property-regex, babel-plugin-syntax-class-properties, babel-plugin-syntax-decorators, babel-plugin-syntax-do-expressions, babel-plugin-syntax-export-default-from, babel-plugin-syntax-flow, babel-plugin-syntax-function-bind, babel-plugin-syntax-function-sent, babel-plugin-syntax-import-assertions, babel-plugin-syntax-jsx, babel-plugin-syntax-module-string-names, babel-plugin-syntax-partial-application, babel-plugin-syntax-pipeline-operator, babel-plugin-syntax-record-and-tuple, babel-plugin-syntax-throw-expressions, babel-plugin-syntax-top-level-await, babel-plugin-syntax-typescript, babel-plugin-transform-arrow-functions, babel-plugin-transform-async-to-generator, babel-plugin-transform-block-scoped-functions, babel-plugin-transform-block-scoping, babel-plugin-transform-classes, babel-plugin-transform-computed-properties, babel-plugin-transform-destructuring, babel-plugin-transform-dotall-regex, babel-plugin-transform-duplicate-keys, babel-plugin-transform-exponentiation-operator, babel-plugin-transform-flow-comments, babel-plugin-transform-flow-strip-types, babel-plugin-transform-for-of, babel-plugin-transform-function-name, babel-plugin-transform-instanceof, babel-plugin-transform-jscript, babel-plugin-transform-literals, babel-plugin-transform-member-expression-literals, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-systemjs, babel-plugin-transform-modules-umd, babel-plugin-transform-named-capturing-groups-regex, babel-plugin-transform-new-target, babel-plugin-transform-object-assign, babel-plugin-transform-object-set-prototype-of-to-assign, babel-plugin-transform-object-super, babel-plugin-transform-parameters, babel-plugin-transform-property-literals, babel-plugin-transform-property-mutators, babel-plugin-transform-proto-to-assign, babel-plugin-transform-react-constant-elements, babel-plugin-transform-react-display-name, babel-plugin-transform-react-inline-elements, babel-plugin-transform-react-jsx-compat, babel-plugin-transform-react-jsx-development, babel-plugin-transform-react-jsx-self, babel-plugin-transform-react-jsx-source, babel-plugin-transform-react-jsx, babel-plugin-transform-react-pure-annotations, babel-plugin-transform-regenerator, babel-plugin-transform-reserved-words, babel-plugin-transform-runtime, babel-plugin-transform-shorthand-properties, babel-plugin-transform-spread, babel-plugin-transform-sticky-regex, babel-plugin-transform-strict-mode, babel-plugin-transform-template-literals, babel-plugin-transform-typeof-symbol, babel-plugin-transform-typescript, babel-plugin-transform-unicode-escapes, babel-plugin-transform-unicode-regex, babel-preset-env, babel-preset-flow, babel-preset-react, babel-preset-typescript, babel-register, babel-standalone, babel-traverse, babel-types
  • #​12186 chore: use workspace:* for dev deps (@​JLHwung)
• babel-compat-data, babel-helper-compilation-targets, babel-helper-create-class-features-plugin, babel-helper-remap-async-to-generator, babel-helper-simple-access, babel-helper-transform-fixture-test-runner, babel-plugin-transform-named-capturing-groups-regex, babel-plugin-transform-object-assign, babel-plugin-transform-parameters, babel-plugin-transform-react-jsx-self, babel-plugin-transform-react-jsx-source, babel-plugin-transform-template-literals, babel-preset-env, babel-preset-react, babel-runtime-corejs2, babel-runtime, babel-standalone
  • #​12175 Remove unused dependencies and devDependencies (@​nicolo-ribaudo)

v7.12.0

Compare Source

:eyeglasses: Spec Compliance

• babel-core, babel-helper-module-transforms, babel-parser, babel-plugin-proposal-export-namespace-from, babel-plugin-syntax-module-string-names, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-systemjs, babel-plugin-transform-modules-umd, babel-types
  • #​12091 String import/export specifier (@​JLHwung)
• babel-parser
  • #​12111 [ts] Throw a syntax error for index signature with declare (@​sosukesuzuki)

:rocket: New Feature

• babel-core, babel-generator, babel-parser, babel-plugin-syntax-import-assertions, babel-plugin-syntax-module-attributes, babel-standalone, babel-types
  • #​12139 Parse import-assertions (@​xtuc)
• babel-core, babel-helper-create-class-features-plugin, babel-helper-module-transforms, babel-helper-replace-supers, babel-plugin-proposal-class-static-block, babel-plugin-transform-modules-commonjs, babel-standalone, babel-traverse, babel-types
  • #​12143 Transform class static block (@​JLHwung)
• babel-generator, babel-parser, babel-plugin-syntax-class-static-block, babel-types
  • #​12079 Parse class static block (@​JLHwung)
• babel-generator, babel-parser, babel-types
  • #​12129 Support TypeScript mapped type 'as' clauses (@​existentialism)
  • #​12147 [ts] Add support for the "intrinsic" keyword (@​nicolo-ribaudo)
• babel-parser, babel-types
  • #​12131 [ts] Add support for template interpolations in types (@​nicolo-ribaudo)
• babel-plugin-transform-modules-systemjs
  • #​12163 SystemJS top-level await support (@​guybedford)
• babel-plugin-transform-typescript, babel-preset-typescript
  • #​11950 Add jsxPragmaFrag support to typescript transform (@​JLHwung)
• babel-core, babel-helper-module-transforms, babel-parser, babel-plugin-proposal-export-namespace-from, babel-plugin-syntax-module-string-names, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-systemjs, babel-plugin-transform-modules-umd, babel-types
  • #​12091 String import/export specifier (@​JLHwung)
• babel-core
  • #​11907 Return a list of files that were read from loadPartialConfig (@​devongovett)

:bug: Bug Fix

• babel-parser
  • #​12167 [ts] Add asserts: false to TSTypePredicate node (@​sosukesuzuki)
  • #​12161 Move check for TSTypeCastExpression to catch another case (@​existentialism)
  • #​12120 Throw a recoverable error for missing initializer in const declaration (@​sosukesuzuki)
  • #​12108 Improve syntax error for class fields in ambient context (@​sosukesuzuki)
  • #​12088 Throw a syntax error for empty type parameter/argument (@​sosukesuzuki)
  • #​12093 Throw an error for a declare class field that have an initializer (@​sosukesuzuki)
  • #​12085 Do not throw an error for optional binding pattern params in function declaration (@​sosukesuzuki)
  • #​12076 Fix invalid setter parse (@​fisker)
  • #​12054 Throw a syntax error for a declare function with a body (@​sosukesuzuki)
  • #​12065 Throw a syntax error for a constructor with type parameters (@​sosukesuzuki)
• babel-plugin-transform-typescript
  • #​12149 fix transform-typescript logic to remove definite fields (@​akphi)
  • #​12122 [transform-typescript] Fix import elision for type exports (@​Amareis)
• babel-helper-member-expression-to-functions, babel-plugin-proposal-class-properties, babel-plugin-proposal-nullish-coalescing-operator, babel-plugin-proposal-optional-chaining
  • #​12032 Handle cases when ?? and ?. is in binding initializers (@​JLHwung)
• babel-helper-builder-react-jsx-experimental, babel-plugin-transform-react-jsx-development, babel-plugin-transform-react-jsx, babel-preset-react
  • #​12116 add .js extension to react runtime for JSX transform (@​lunaruan)
• babel-traverse, babel-types
  • #​12119 fix: mark Pattern in CatchClause as scope (@​JLHwung)
• babel-generator
  • #​12114 Fix printing TSTypeOperator (@​existentialism)
  • #​12082 Ensure expressions wrapped in parens (@​overlookmotel)
  • #​12081 Fix @babel/generator does not print decorators of private properties (@​zweimach)
  • #​12086 Add sourcemap markings for each line of a string (@​jridgewell)
• babel-plugin-transform-modules-systemjs
  • #​12110 Fix reexporting init-less variable in systemjs (@​JLHwung)
• babel-helper-module-transforms, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-umd, babel-plugin-transform-runtime
  • #​11739 [cjs] Skip duplicate reexported bindings in namespace reexports (@​mischnic)
• babel-helper-create-regexp-features-plugin, babel-plugin-transform-unicode-regex
  • #​12077 Bump regexpu-core (@​existentialism)
• babel-plugin-proposal-do-expressions, babel-traverse
  • #​11728 fix(do-expr): SwitchStatement with IfStatement cases (@​barronwei)

:nail_care: Polish

• babel-parser
  • #​12072 [parser] Better error message for missing number exponent (@​iamfotx)
  • #​12061 Throw a syntax error for a parameter properties in not constructor (@​sosukesuzuki)
• babel-helper-compilation-targets, babel-helper-validator-option, babel-preset-env
  • #​12006 refactor: add @​babel/helper-validator-option (@​JLHwung)

:house: Internal

• babel-cli, babel-helper-transform-fixture-test-runner, babel-traverse
  • #​11797 Replace lodash 'defaults' usage with ES6 Spread initializer (@​jayaddison)
• babel-plugin-transform-runtime, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • #​10853 Specify runtime exports (@​JLHwung)
• babel-core
  • #​11689 Instantiate presets before plugins (@​nicolo-ribaudo)
• babel-plugin-proposal-logical-assignment-operators, babel-plugin-proposal-numeric-separator, babel-plugin-syntax-import-meta, babel-plugin-syntax-logical-assignment-operators, babel-plugin-syntax-numeric-separator, babel-plugin-transform-modules-systemjs, babel-preset-env, babel-standalone
  • #​12117 Archive plugins (@​JLHwung)
• Other
  • #​12154 chore: bump gulp-cli to 2.3.0 (@​JLHwung)
  • #​12134 Yarn 2.3 (@​nicolo-ribaudo)
  • #​12099 fix: apply terser plugin only on *.min.js (@​JLHwung)
  • #​12098 docs: update build required node version (@​JLHwung)
  • #​12078 Bump Babel deps (@​existentialism)
  • #​12070 chore: pin browserslist version to 4.12.0 (@​JLHwung)
  • #​12063 chore: add git-blame-ignore-revs (@​JLHwung)
  • #​12049 chore: use latest node on ci workflow when possible (@​JLHwung)
• babel-compat-data, babel-preset-env
  • #​12118 chore: bump electron-to-chromium (@​JLHwung)
• babel-parser
  • #​12103 Add missing tests for TypeScript syntax errors (@​sosukesuzuki)
• babel-core, babel-plugin-transform-runtime
  • #​12102 docs: Fix simple typo, preprelease -> pre-release (@​timgates42)
• babel-compat-data
  • #​12044 chore: remove unused dependencies (@​JLHwung)

</details>

<details> <summary>typescript-eslint/typescript-eslint</summary>

v4.4.1

Compare Source

Bug Fixes

• eslint-plugin: [ban-ts-comment] support block comments (#​2644) (9c3c686)
• eslint-plugin: [ban-types] allow banning types with specific parameters (#​2662) (77732a2)
• eslint-plugin: [consistent-type-assertions] check type assertion in jsx props (#​2653) (393e925)
• eslint-plugin: [no-duplicate-imports] distinguish member, default (#​2637) (c71f423)
• eslint-plugin: [no-throw-literal] false positive with logical expressions (#​2645) (57aa6c7)
• eslint-plugin: [no-unused-vars] fix false positives for duplicated names in namespaces (#​2659) (0d696c7)
• eslint-plugin: [no-use-before-define] correctly handle typeof type references (#​2623) (8e44c78)
• scope-manager: don't create a variable for global augmentation (#​2639) (6bc9325)

</details>

<details> <summary>paulmillr/chokidar</summary>

v3.4.3

Compare Source

</details>

<details> <summary>prettier/eslint-config-prettier</summary>

v6.13.0

Compare Source

• Added: New rules in [eslint-plugin-vue] 7.0 (which supports Vue 3.0). Thanks to @​xcatliu!

</details>

<details> <summary>facebook/jest</summary>

v26.5.3

Compare Source

Features

• [jest-runtime] add support for dynamic import() from CommonJS (#​10620)

Fixes

• [jest-runner, jest-runtime] require.main should not be undefined with createRequire() (#​10610)
• [jest-runtime] add missing module.path property (#​10615)
• [jest-runtime] Add mainModule instance variable to runtime (#​10621)
• [jest-runtime] Evaluate Node core modules on dynamic import() (#​10622)
• [jest-validate] Show suggestion only when unrecognized cli param is longer than 1 character (#​10604)
• [jest-validate] Validate testURL as CLI option (#​10595)

</details>

<details> <summary>okonet/lint-staged</summary>

v10.4.2

Compare Source

Bug Fixes

• update docs on supported config file extensions (#​917) (78782f9)

v10.4.1

Compare Source

Bug Fixes

• add support for .cjs configs (#​909) (36e7e58)

</details>

<details> <summary>rollup/rollup</summary>

v2.32.0

Compare Source

2020-10-16

Features

• Extend preserveEntrySignatures with a value "exports-only" to allow extension only if an entry does not have exports (#​3823)

Pull Requests

• #​3823: Add "exports-only" option to preserveSignature (@​lukastaegert)

v2.31.0

Compare Source

2020-10-15

Features

• When using the output.moduleToStringTag option, also add the tag to entries with exports and simulated external namespaces (#​3822)
• Add the __esModule interop marker to IIFE global variables unless output.esModule is turned off (#​3822)

Pull Requests

• #​3822: Add module toStringTag to entries and interop namespaces (@​lukastaegert)

v2.30.0

Compare Source

2020-10-13

Features

• Add moduleParsed hook that is called for each module once code and AST are available (#​3813)
• Include code and AST in this.getModuleInfo (#​3813)

Bug Fixes

• Provide the original Acorn AST instead of the internal one when resolving dynamic imports that contain non-trivial expressions (#​3813)

Pull Requests

• #​3813: Add moduleParsed plugin hook (@​lukastaegert)
• #​3815: Docs: wile => while (@​tjenkinson)
• #​3817: Docs: fix code snippet (@​codefrau)
• #​3818: Update documentation on configuring Babel, removing the section on passing '{"modules": false}' as that is no longer needed since Babel 7 (@​Robin-Hoodie)

</details>

<details> <summary>ezolenko/rollup-plugin-typescript2</summary>

v0.28.0

Compare Source

#​221

</details>

<details> <summary>lovell/sharp</summary>

v0.26.2

Compare Source

</details>

<details> <summary>TypeStrong/ts-loader</summary>

v8.0.5

Compare Source

• Fixed deprecation warnings on webpack@5 - thanks @​sanex3339

</details>

Renovate configuration

:date: Schedule: "after 3am on Wednesday" (UTC).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

Describe the bug I want to use the Bridge-Pattern with a few more options enabled.

I enabled all options i wanted by reading the documentation:

"allowlist": {
    "all": false,
    "event": true,
    "open": true,
    "openDialog": true
}

When i tried to use the http module from tauri this error was printed:

[ERROR] "httpRequest' not on the allowlist (https://tauri.studio/docs/api/config#tauri.allowlist)"

This option isn't in the docs but tried anyway and now cargo printed the following error:

error: failed to select a version for `tauri`.
    ... required by package `<application_name> v0.1.0 (<application_path>/src-tauri)`
versions that meet the requirements `=0.9.2` are: 0.9.2

the package `<application_name>` depends on `tauri`, with features: `http-request` but `tauri` does not have these features.


failed to select a version for `tauri` which could resolve this conflict

To Reproduce Steps to reproduce the behavior:

1. Go to src-tauri/tauri.conf.json
2. Add "httpRequest": true, to tauri:allowlist
3. Use for example:

import http from 'tauri/api/http'
http.get('https://google.com')

4. Start tauri application
5. Look at the output of tauri dev

Expected behavior When I add the httpRequest option to the allow list I want the application to compile and the ability to use the http module from JavaScript.

Platform and Versions: OS: Linux(5.8.10-arch1-1) - linux/x64 Node: 14.11.0 NPM: 6.14.7 Yarn: 1.22.5 Rustc: 1.46.0

What kind of change does this PR introduce? (check at least one)

• [x] Bugfix
• [ ] Feature
• [ ] New Binding Issue #___
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

• [ ] Yes. Issue #___
• [x] No

The PR fulfills these requirements:

• [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

After calling API functions too many times they will fail with TypeError: Unable to delete property., but only when the Web Inspector is not open. When the Web Inspector is open, it works fine.

Minimal reproducible examples:

async function writeTooManyTextFiles() {
  for(let i=0; i<300; i++) {
    console.log("writeTooManyTextFiles", i)
    await writeFile({path: '/Users/racoon/test.txt', contents: 'Testing'})
  }
}

async function readTooManyTextFiles() {
  for(let i=0; i<300; i++) {
    console.log("readTooManyTextFiles", i)
    const text = await readTextFile('/Users/racoon/test.txt')
  }
}

async function readTooManyDirectories() {
  for(let i=0; i<300; i++) {
    console.log("readTooManyDirectories", i)
    const text = await readDir('/Users/racoon/')
  }
}

They fail consistently for me after 168 files with error TypeError: Unable to delete property..

This error is thrown by at Reflect.deleteProperty(window, error) at line 70 of cli/tauri.js/api-src/tauri.ts

This error is strange because I checked and the property does exist on the window object. It seems after calling readTextFile more than 168 times, all calls to Reflect.deleteProperty will fail with this error.

I have reproduced this on Mac and Ubuntu

Here is the issue boiled down to just the combination of Promises and using Reflect.deleteProperty(). This shows the problem is the way cli/tauri.js/api-src/tauri.ts promisifies the api calls and not the API calls themselfs:

function bar() {
  return new Promise((resolve, reject) => {
    const p = Math.random().toString(36).substring(7);
    try {
      Object.defineProperty(window, p, {
        value: p
      });
    } catch (e) {
      reject(e)
    }
    setTimeout(() => {
      try {
        Reflect.deleteProperty(window, p)
        resolve()
      } catch (e) {
        reject(e)
      }
    }, 0);
  })
}

async function foo() {
  for(let i=0; i<3000; i++) {
    console.log("foo", i)
    await bar()
  }
}

Output:

...
[Log] foo – 132
[Log] foo – 133
[Log] foo – 134
[Log] foo – 135
[Log] foo – 136
[Log] foo – 137
[Log] foo – 138
[Error] error loading data – TypeError: Unable to delete property.
TypeError: Unable to delete property.
	_callee4$ (index.js:1126)
	tryCatch (runtime.js:63)
	invoke (runtime.js:293)
	asyncGeneratorStep (asyncToGenerator.js:9)
	_throw (asyncToGenerator.js:35)
	promiseReactionJob

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

• [x] Bugfix
• [ ] Feature
• [ ] New Binding Issue #___
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

• [ ] Yes. Issue #___
• [x] No

The PR fulfills these requirements:

• [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

See #1038

dirs is unmaintained, use dirs-next instead

The dirs crate is not maintained any more; use dirs-next instead.

See advisory page for additional details.

Closed by #1057.

dirs is unmaintained, use dirs-next instead

The dirs crate is not maintained any more; use dirs-next instead.

See advisory page for additional details.

Closed by #1057.

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

• [ ] Bugfix
• [ ] Feature
• [ ] New Binding Issue #___
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [x] Other, please describe: dependency change (dirs unmaintained)

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

• [ ] Yes. Issue #___
• [x] No

The PR fulfills these requirements:

• [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

This resolves an audit warning because which v3.x depended on failure, which if officially deprecated/unmaintained.

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

• [ ] Bugfix
• [ ] Feature
• [ ] New Binding Issue #___
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [x] Other, please describe: test update

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

• [ ] Yes. Issue #___
• [x] No

The PR fulfills these requirements:

• [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• [ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Just updating the internal e2e test so we can use it.

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

• [ ] Bugfix
• [ ] Feature
• [ ] New Binding Issue #___
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [x] Other, please describe: test update

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

• [ ] Yes. Issue #___
• [x] No

The PR fulfills these requirements:

• [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• [ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Just updating the internal e2e test so we can use it.

This PR contains the following updates:

Renovate configuration

:date: Schedule: "after 3am on Wednesday" (UTC).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

This PR contains the following updates:

Release Notes

<details> <summary>sindresorhus/is-reachable</summary>

v5.0.0

Compare Source

Breaking

• Require Node.js 10 (#​48) 50d61e8

Fixes

• Fix timeout handling (#​48) 50d61e8

</details>

<details> <summary>webpack/webpack</summary>

v5.1.3

Compare Source

Bugfixes

• omit unused modules from chunks when modules are only unused in some runtimes
  • fixes Self-reference dependency has unused export name error
• fix order of asset optimization to fix conflict between compression-plugin and real hash plugin

v5.1.2

Compare Source

Bugfixes

• revert: omit unused modules from chunk when modules are only unused in some runtimes
  • caused issues with mini-css modules

v5.1.1

Compare Source

Bugfixes

• fix order of chunk hashing to allow to uses hashes in WebWorkers
• update to terser-webpack-plugin 5
  • reduces number of dependencies by dropping webpack 4 support
• omit unused modules from chunk when modules are only unused in some runtimes
  • fixes Self-reference dependency has unused export name error
• fix hanging production builds because of infinite loop in inner graph optimization
• Compilation.deleteAsset updates chunk to file mappings

v5.1.0

Compare Source

Features

• expose webpack property from Compiler
• expose cleverMerge, EntryOptionPlugin, DynamicEntryPlugin

Bugfixes

• missing require("..").xxx in try-catch produces a warning instead of an error now
• handle reexports in concatenated modules correctly when they are side-effect-free
• fix incorrect deprecation message for ModuleTemplate.hooks.hash

v5.0.0

Compare Source

Announcement and changelog

</details>

<details> <summary>webpack/webpack-cli</summary>

v4.0.0

Compare Source

Bug Fixes

• add compilation lifecycle in watch instance (#​1903) (02b6d21)
• cleanup package-utils package (#​1822) (fd5b92b)
• cli-executer supplies args further up (#​1904) (097564a)
• exit code for validation errors (59f6303)
• exit process in case of schema errors (71e89b4)

Features

• assign config paths in build dependencies in cache config (#​1900) (7e90f11)

</details>

Renovate configuration

:date: Schedule: "after 3am on Wednesday" (UTC).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

This PR contains the following updates:

Renovate configuration

:date: Schedule: "after 3am on Wednesday" (UTC).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Never, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

This PR contains the following updates:

Renovate configuration

:date: Schedule: "after 3am on Wednesday" (UTC).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

• [ ] Bugfix
• [ ] Feature
• [ ] New Binding Issue #___
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [x] Other, please describe: dependency change (dirs unmaintained)

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

• [ ] Yes. Issue #___
• [x] No

The PR fulfills these requirements:

• [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

• [x] Bugfix
• [ ] Feature
• [ ] New Binding Issue #___
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

• [ ] Yes. Issue #___
• [x] No

The PR fulfills these requirements:

• [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

See #1038

Hmm I thought https://github.com/webview/webview/pull/405 would fix this. @abeMedia do you know something about this?

I can reproduce it with the readTooManyDirectories call and it seems like configurable: true is the fix here. I'll PR it.

I have no idea, seems like the problem only happens after some time? Maybe it's an invalid property name and it won't happen with me since it's random, i don't know. I was using the bar and foo function examples from above to try to reproduce it.

If configurable as true fix it, then we should just PR it and hope it doesn't happen anymore.

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one) <!-- If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->

• [x] Bugfix
• [ ] Feature
• [ ] New Binding Issue #___
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one) <!-- If yes, please describe the impact and migration path for existing applications in an attached issue. Filing a PR with breaking changes that has not been discussed and approved by the maintainers in an issue will be immediately closed. -->

• [ ] Yes. Issue #___
• [x] No

The PR fulfills these requirements:

• [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

What kind of change does this PR introduce? (check at least one)

• [x] Bugfix
• [ ] Feature
• [ ] New Binding Issue #___
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

• [ ] Yes. Issue #___
• [x] No

The PR fulfills these requirements:

• [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• [x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Well I never would've thought of a node user without npm, but that actually makes sense given how bad it is LOL thanks for the report!

I can't reproduce this on macOS. Can one of you see if adding configurable: true to the Object.defineProperty call fixes it? Like this:

Object.defineProperty(window, identifier, { 
   value: (result: any) => { 
     if (once) { 
       Reflect.deleteProperty(window, identifier) 
     } 
  
     return callback?.(result) 
   }, 
   writable: false,
   configurable: true
 }) 

I'll fix this tonight. For now you could use all: true

Hmm I can't reproduce this on my Linux. Will try on mac later.

I think this won't work on Windows. I'll investigate this.

Description of change

Implementing the event notification through polling.

Type of change

• Enhancement (a non-breaking change which adds functionality)

How the change has been tested

Not tested yet, will do after the Hornet tests.

Change checklist

• [x] I have followed the contribution guidelines for this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have checked that new and existing unit tests pass locally with my changes