Configure Wrangler in the format of your choice.

Last update: Oct 5, 2022

Overview

wjson

✨ Configure Wrangler in the format of your choice. ✨

Installation

npm i -D @darkflare/wjson

Usage (CLI)

Run the below command and wjson will automatically search for your configuration file and generate a wrangler.toml for you.

wjson

Automatically Detectable Files

wrangler.json
wrangler.js
wrangler.mjs
wrangler.cjs
wrangler.ts
wrangler.yaml
wrangler.yml

Options

--config to use a custom config, e.g. wjson --config="./my.json"

Usage (API)

import { join } from 'node:path'
import { generateConfig, parseConfig } from 'wjson'

// get the config from a file
const config = await parseConfig(join(someDirectory, './custom.json'))

// alternatively, you can only specify the directory name
const config = await parseConfig(someDirectory)

// generate a wrangler.toml from a config
await generateConfig(config)

Config Files

json

{
  "$schema": "https://raw.githubusercontent.com/azurydev/wjson/dev/schema.json",
  // your config (w/ autocomplete)
}

js/mjs/ts

import { defineConfig } from 'wjson'

export default defineConfig({
 // your config (w/ autocomplete)
})

js/cjs

const { defineConfig } = require('wjson')

module.exports = defineConfig({
 // your config (w/ autocomplete)
})

yaml/yml

accountId: '0123456789'

development:
  name: 'my-awesome-worker'

# your config

Config Syntax

all options must be specified in camelCase
vars option was renamed to variables
nodeComp option was renamed to nodeCompatibility
any environment-related options must be specified under development (global, default), staging, or production

Comments

chore(deps-dev): bump @changesets/cli from 2.24.3 to 2.25.0
Bumps @changesets/cli from 2.24.3 to 2.25.0.

Release notes

Sourced from @changesets/cli's releases.

@changesets/cli@2.25.0

Minor Changes

#662 8c08469 Thanks @JakeGinnivan! - Private packages can now be tagged in the same way public packages do when they are published to npm.

To enable set privatePackages: { version: true, tag: true } in your config.json.

You can also now opt private packages out of versioning entirely by setting privatePackages: false.

Patch Changes

#953 98d63e0 Thanks @alexamy! - Add a new line at the end of the default config file generated when invoking changeset init.

#949 64585ea Thanks @Andarist, @BPScott! - Fixed the issue that caused transitive dependents of dev dependents to be bumped when a package got bumped and when using ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.updateInternalDependents: "always". To illustrate this with an example:

pkg-a - version: 1.0.0 pkg-b - devDependencies['pkg-a']: 1.0.0 pkg-c - dependencies['pkg-b']: 1.0.0

With a changeset for pkg-a the pkg-c could have been sometimes incorrectly released.

Updated dependencies [8c08469, 8c08469, 64585ea]:

@changesets/git@1.5.0

@changesets/config@2.2.0

@changesets/types@5.2.0

@changesets/assemble-release-plan@5.2.2

@changesets/apply-release-plan@6.1.1

@changesets/read@0.5.8

@changesets/get-release-plan@3.0.15

@changesets/changelog-git@0.1.13

@changesets/get-dependents-graph@1.3.4

@changesets/pre@1.0.13

@changesets/write@0.2.1

@changesets/cli@2.24.4

Patch Changes

Updated dependencies [c140171]:

@changesets/apply-release-plan@6.1.0

@changesets/write@0.2.0

Commits

26c9c73 Version Packages (#950)

8c08469 Add support for tagging private packages when their version changes (#662)

98d63e0 Add a new line at the end of the default config file generated when invoking ...

911f314 Fix types to avoid @ts-ignore (#951)

64585ea Fixed an issue with incorrect dependent updates on none changesets with `upda...

eb787ea Fixed markdown lists in CHANGELOGs (#939)

6337ae3 Version Packages (#931)

c140171 Prefer local Prettier when formatting files (#905)

8e64d41 Add The Guild libraries to list of Changesets adopters (#792)

af97819 Fixed typos & grammar in automating-changesets.md (#917)

See full diff in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 2
chore(deps-dev): bump @types/node from 18.7.9 to 18.8.0
Bumps @types/node from 18.7.9 to 18.8.0.

Commits

See full diff in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 2
chore(deps-dev): bump @changesets/changelog-github from 0.4.6 to 0.4.7
Bumps @changesets/changelog-github from 0.4.6 to 0.4.7.

Release notes

Sourced from @changesets/changelog-github's releases.

@changesets/changelog-github@0.4.7

Patch Changes

Updated dependencies [8c08469]:

@changesets/types@5.2.0

Commits

26c9c73 Version Packages (#950)

8c08469 Add support for tagging private packages when their version changes (#662)

98d63e0 Add a new line at the end of the default config file generated when invoking ...

911f314 Fix types to avoid @ts-ignore (#951)

64585ea Fixed an issue with incorrect dependent updates on none changesets with `upda...

eb787ea Fixed markdown lists in CHANGELOGs (#939)

6337ae3 Version Packages (#931)

c140171 Prefer local Prettier when formatting files (#905)

8e64d41 Add The Guild libraries to list of Changesets adopters (#792)

af97819 Fixed typos & grammar in automating-changesets.md (#917)

Additional commits viewable in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 2
chore(deps): bump esbuild from 0.15.5 to 0.15.10
Bumps esbuild from 0.15.5 to 0.15.10.

Release notes

Sourced from esbuild's releases.

v0.15.10

Add support for node's "pattern trailers" syntax (#2569)

After esbuild implemented node's exports feature in package.json, node changed the feature to also allow text after * wildcards in patterns. Previously the * was required to be at the end of the pattern. It lets you do something like this:

{ "exports": { "./features/*": "./features/*.js", "./features/*.js": "./features/*.js" } }

With this release, esbuild now supports these types of patterns too.

Fix subpath imports with Yarn PnP (#2545)

Node has a little-used feature called subpath imports which are package-internal imports that start with # and that go through the imports map in package.json. Previously esbuild had a bug that caused esbuild to not handle these correctly in packages installed via Yarn's "Plug'n'Play" installation strategy. The problem was that subpath imports were being checked after Yarn PnP instead of before. This release reorders these checks, which should allow subpath imports to work in this case.

Link from JS to CSS in the metafile (#1861, #2565)

When you import CSS into a bundled JS file, esbuild creates a parallel CSS bundle next to your JS bundle. So if app.ts imports some CSS files and you bundle it, esbuild will give you app.js and app.css. You would then add both <script src="app.js"></script> and <link href="app.css" rel="stylesheet"> to your HTML to include everything in the page. This approach is more efficient than having esbuild insert additional JavaScript into app.js that downloads and includes app.css because it means the browser can download and parse both the CSS and the JS in parallel (and potentially apply the CSS before the JS has even finished downloading).

However, sometimes it's difficult to generate the <link> tag. One case is when you've added [hash] to the entry names setting to include a content hash in the file name. Then the file name will look something like app-GX7G2SBE.css and may change across subsequent builds. You can tell esbuild to generate build metadata using the metafile API option but the metadata only tells you which generated JS bundle corresponds to a JS entry point (via the entryPoint property), not which file corresponds to the associated CSS bundle. Working around this was hacky and involved string manipulation.

This release adds the cssBundle property to the metafile to make this easier. It's present on the metadata for the generated JS bundle and points to the associated CSS bundle. So to generate the HTML tags for a given JS entry point, you first find the output file with the entryPoint you are looking for (and put that in a <script> tag), then check for the cssBundle property to find the associated CSS bundle (and put that in a <link> tag).

One thing to note is that there is deliberately no jsBundle property mapping the other way because it's not a 1:1 relationship. Two JS bundles can share the same CSS bundle in the case where the associated CSS bundles have the same name and content. In that case there would be no one value for a hypothetical jsBundle property to have.

v0.15.9

Fix an obscure npm package installation issue with --omit=optional (#2558)

The previous release introduced a regression with npm install esbuild --omit=optional where the file node_modules/.bin/esbuild would no longer be present after installation. That could cause any package scripts which used the esbuild command to no longer work. This release fixes the regression so node_modules/.bin/esbuild should now be present again after installation. This regression only affected people installing esbuild using npm with either the --omit=optional or --no-optional flag, which is a somewhat unusual situation.

More details:

The reason for this regression is due to some obscure npm implementation details. Since the Go compiler doesn't support trivial cross-compiling on certain Android platforms, esbuild's installer installs a WebAssembly shim on those platforms instead. In the previous release I attempted to simplify esbuild's WebAssembly shims to depend on the esbuild-wasm package instead of including another whole copy of the WebAssembly binary (to make publishing faster and to save on file system space after installation). However, both the esbuild package and the esbuild-wasm package provide a binary called esbuild and it turns out that adding esbuild-wasm as a nested dependency of the esbuild package (specifically esbuild optionally depends on @esbuild/android-arm which depends on esbuild-wasm) caused npm to be confused about what node_modules/.bin/esbuild is supposed to be.

It's pretty strange and unexpected that disabling the installation of optional dependencies altogether would suddenly cause an optional dependency's dependency to conflict with the top-level package. What happens under the hood is that if --omit=optional is present, npm attempts to uninstall the esbuild-wasm nested dependency at the end of npm install (even though the esbuild-wasm package was never installed due to --omit=optional). This uninstallation causes node_modules/.bin/esbuild to be deleted.

After doing a full investigation, I discovered that npm's handling of the .bin directory is deliberately very brittle. When multiple packages in the dependency tree put something in .bin with the same name, the end result is non-deterministic/random. What you get in .bin might be from one package, from the other package, or might be missing entirely. The workaround suggested by npm is to just avoid having two packages that put something in .bin with the same name. So this was fixed by making the @esbuild/android-arm and esbuild-android-64 packages each include another whole copy of the WebAssembly binary, which works because these packages don't put anything in .bin.

v0.15.8

Fix JSX name collision edge case (#2534)

Code generated by esbuild could have a name collision in the following edge case:

The JSX transformation mode is set to automatic, which causes import statements to be inserted

An element uses a {...spread} followed by a key={...}, which uses the legacy createElement fallback imported from react

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.15.10

Add support for node's "pattern trailers" syntax (#2569)

After esbuild implemented node's exports feature in package.json, node changed the feature to also allow text after * wildcards in patterns. Previously the * was required to be at the end of the pattern. It lets you do something like this:

{ "exports": { "./features/*": "./features/*.js", "./features/*.js": "./features/*.js" } }

With this release, esbuild now supports these types of patterns too.

Fix subpath imports with Yarn PnP (#2545)

Node has a little-used feature called subpath imports which are package-internal imports that start with # and that go through the imports map in package.json. Previously esbuild had a bug that caused esbuild to not handle these correctly in packages installed via Yarn's "Plug'n'Play" installation strategy. The problem was that subpath imports were being checked after Yarn PnP instead of before. This release reorders these checks, which should allow subpath imports to work in this case.

Link from JS to CSS in the metafile (#1861, #2565)

When you import CSS into a bundled JS file, esbuild creates a parallel CSS bundle next to your JS bundle. So if app.ts imports some CSS files and you bundle it, esbuild will give you app.js and app.css. You would then add both <script src="app.js"></script> and <link href="app.css" rel="stylesheet"> to your HTML to include everything in the page. This approach is more efficient than having esbuild insert additional JavaScript into app.js that downloads and includes app.css because it means the browser can download and parse both the CSS and the JS in parallel (and potentially apply the CSS before the JS has even finished downloading).

However, sometimes it's difficult to generate the <link> tag. One case is when you've added [hash] to the entry names setting to include a content hash in the file name. Then the file name will look something like app-GX7G2SBE.css and may change across subsequent builds. You can tell esbuild to generate build metadata using the metafile API option but the metadata only tells you which generated JS bundle corresponds to a JS entry point (via the entryPoint property), not which file corresponds to the associated CSS bundle. Working around this was hacky and involved string manipulation.

This release adds the cssBundle property to the metafile to make this easier. It's present on the metadata for the generated JS bundle and points to the associated CSS bundle. So to generate the HTML tags for a given JS entry point, you first find the output file with the entryPoint you are looking for (and put that in a <script> tag), then check for the cssBundle property to find the associated CSS bundle (and put that in a <link> tag).

One thing to note is that there is deliberately no jsBundle property mapping the other way because it's not a 1:1 relationship. Two JS bundles can share the same CSS bundle in the case where the associated CSS bundles have the same name and content. In that case there would be no one value for a hypothetical jsBundle property to have.

0.15.9

Fix an obscure npm package installation issue with --omit=optional (#2558)

The previous release introduced a regression with npm install esbuild --omit=optional where the file node_modules/.bin/esbuild would no longer be present after installation. That could cause any package scripts which used the esbuild command to no longer work. This release fixes the regression so node_modules/.bin/esbuild should now be present again after installation. This regression only affected people installing esbuild using npm with either the --omit=optional or --no-optional flag, which is a somewhat unusual situation.

More details:

The reason for this regression is due to some obscure npm implementation details. Since the Go compiler doesn't support trivial cross-compiling on certain Android platforms, esbuild's installer installs a WebAssembly shim on those platforms instead. In the previous release I attempted to simplify esbuild's WebAssembly shims to depend on the esbuild-wasm package instead of including another whole copy of the WebAssembly binary (to make publishing faster and to save on file system space after installation). However, both the esbuild package and the esbuild-wasm package provide a binary called esbuild and it turns out that adding esbuild-wasm as a nested dependency of the esbuild package (specifically esbuild optionally depends on @esbuild/android-arm which depends on esbuild-wasm) caused npm to be confused about what node_modules/.bin/esbuild is supposed to be.

It's pretty strange and unexpected that disabling the installation of optional dependencies altogether would suddenly cause an optional dependency's dependency to conflict with the top-level package. What happens under the hood is that if --omit=optional is present, npm attempts to uninstall the esbuild-wasm nested dependency at the end of npm install (even though the esbuild-wasm package was never installed due to --omit=optional). This uninstallation causes node_modules/.bin/esbuild to be deleted.

After doing a full investigation, I discovered that npm's handling of the .bin directory is deliberately very brittle. When multiple packages in the dependency tree put something in .bin with the same name, the end result is non-deterministic/random. What you get in .bin might be from one package, from the other package, or might be missing entirely. The workaround suggested by npm is to just avoid having two packages that put something in .bin with the same name. So this was fixed by making the @esbuild/android-arm and esbuild-android-64 packages each include another whole copy of the WebAssembly binary, which works because these packages don't put anything in .bin.

0.15.8

Fix JSX name collision edge case (#2534)

Code generated by esbuild could have a name collision in the following edge case:

... (truncated)

Commits

aaae34e publish 0.15.10 to npm

4bd03f3 fix #1861, fix #2565: add cssBundle to metafile

c55000d Fix subpath imports with Yarn PnP (#2547)

1bce251 fix transform tsconfigRaw type (#2568)

efd0af6 fix #2569: support node's "pattern trailer" syntax

23709e2 makefile: fix build validation bug

085265a publish 0.15.9 to npm

f84de90 use a custom message for macOS architecture issues

ba91ed1 makefile: publish four at a time again

e55f980 add validate to clean

Additional commits viewable in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 2
chore(deps-dev): bump typescript from 4.7.4 to 4.8.4
Bumps typescript from 4.7.4 to 4.8.4.

Release notes

Sourced from typescript's releases.

TypeScript 4.8.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

fixed issues query for Typescript 4.8.0 (Beta).

fixed issues query for Typescript 4.8.1 (RC).

fixed issues query for Typescript 4.8.2 (Stable).

fixed issues query for Typescript 4.8.3 (Stable).

fixed issues query for Typescript 4.8.4 (Stable).

Downloads are available on:

npm

Visual Studio 2022/2019 (Select new version in project options)

NuGet package

TypeScript 4.8.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

fixed issues query for Typescript 4.8.0 (Beta).

fixed issues query for Typescript 4.8.1 (RC).

fixed issues query for Typescript 4.8.2 (Stable).

fixed issues query for Typescript 4.8.3 (Stable).

Downloads are available on:

npm

Visual Studio 2022/2019 (Select new version in project options)

NuGet package

TypeScript 4.8

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

fixed issues query for Typescript 4.8.0 (Beta).

fixed issues query for Typescript 4.8.1 (RC).

fixed issues query for Typescript 4.8.1 (Stable).

Downloads are available on:

npm

Visual Studio 2022/2019 (Select new version in project options)

NuGet package

TypeScript 4.8 RC

For release notes, check out the release announcement.

... (truncated)

Commits

a614119 Bump version to 4.8.4 and LKG

369b4d8 Cherry pick #50537 and #50779 to release-4.8 (#50907)

41e1ade Cherry-pick PR #50704 into release-4.8 (#50741)

2acf3a3 Cherry-pick PR #50691 into release-4.8 (#50743)

39576e6 Cherry-pick PR #50673 into release-4.8 (#50742)

5773723 Cherry-pick #50724 to release-4.8 (#50760)

a3b3555 Cherry-pick PR #50797 into release-4.8 (#50798)

bb8cf90 Handle more places where package direcroy is converted to canonical file path...

ea348f6 Bump version to 4.8.3 and LKG

6bb16f1 Cherry-pick PR #50620 into release-4.8 (#50676)

Additional commits viewable in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 2
chore(deps-dev): bump @types/node from 18.7.9 to 18.7.23
Bumps @types/node from 18.7.9 to 18.7.23.

Commits

See full diff in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 2
chore(deps-dev): bump eslint from 8.22.0 to 8.24.0
Bumps eslint from 8.22.0 to 8.24.0.

Release notes

Sourced from eslint's releases.

v8.24.0

Features

1729f9e feat: account for sourceType: "commonjs" in the strict rule (#16308) (Milos Djermanovic)

b0d72c9 feat: add rule logical-assignment-operators (#16102) (fnx)

f02bcd9 feat: array-callback-return support findLast and findLastIndex (#16314) (Sosuke Suzuki)

Documentation

2c152ff docs: note false positive Object.getOwnPropertyNames in prefer-reflect (#16317) (AnnAngela)

bf7bd88 docs: fix warn severity description for new config files (#16324) (Nitin Kumar)

8cc0bbe docs: use more clean link syntax (#16309) (Percy Ma)

6ba269e docs: fix typo (#16288) (jjangga0214)

Chores

131e646 chore: Upgrade @humanwhocodes/config-array for perf (#16339) (Nicholas C. Zakas)

504fe59 perf: switch from object spread to Object.assign when merging globals (#16311) (Milos Djermanovic)

v8.23.1

Bug Fixes

b719893 fix: Upgrade eslintrc to stop redefining plugins (#16297) (Brandon Mills)

734b54e fix: improve autofix for the prefer-const rule (#16292) (Nitin Kumar)

6a923ff fix: Ensure that glob patterns are normalized (#16287) (Nicholas C. Zakas)

c6900f8 fix: Ensure globbing doesn't include subdirectories (#16272) (Nicholas C. Zakas)

Documentation

16cba3f docs: fix mobile double tap issue (#16293) (Sam Chen)

e098b5f docs: keyboard control to search results (#16222) (Shanmughapriyan S)

1b5b2a7 docs: add Consolas font and prioritize resource loading (#16225) (Amaresh S M)

1ae8236 docs: copy & use main package version in docs on release (#16252) (Jugal Thakkar)

279f0af docs: Improve id-denylist documentation (#16223) (Mert Ciflikli)

Chores

38e8171 perf: migrate rbTree to js-sdsl (#16267) (Zilong Yao)

1c388fb chore: switch nyc to c8 (#16263) (唯然)

67db10c chore: enable linting .eleventy.js again (#16274) (Milos Djermanovic)

42bfbd7 chore: fix npm run perf crashes (#16258) (唯然)

v8.23.0

Features

3e5839e feat: Enable eslint.config.js lookup from CLI (#16235) (Nicholas C. Zakas)

30b1a2d feat: add allowEmptyCase option to no-fallthrough rule (#15887) (Amaresh S M)

43f03aa feat: no-warning-comments support comments with decoration (#16120) (Lachlan Hunt)

Documentation

b1918da docs: package.json conventions (#16206) (Patrick McElhaney)

0e03c33 docs: remove word immediately (#16217) (Strek)

c6790db docs: add anchor link for "migrating from jscs" (#16207) (Percy Ma)

7137344 docs: auto-generation edit link (#16213) (Percy Ma)

Chores

2e004ab chore: upgrade @eslint/eslintrc@1.3.1 (#16249) (Milos Djermanovic)

... (truncated)

Changelog

Sourced from eslint's changelog.

v8.24.0 - September 23, 2022

131e646 chore: Upgrade @humanwhocodes/config-array for perf (#16339) (Nicholas C. Zakas)

2c152ff docs: note false positive Object.getOwnPropertyNames in prefer-reflect (#16317) (AnnAngela)

bf7bd88 docs: fix warn severity description for new config files (#16324) (Nitin Kumar)

504fe59 perf: switch from object spread to Object.assign when merging globals (#16311) (Milos Djermanovic)

1729f9e feat: account for sourceType: "commonjs" in the strict rule (#16308) (Milos Djermanovic)

b0d72c9 feat: add rule logical-assignment-operators (#16102) (fnx)

f02bcd9 feat: array-callback-return support findLast and findLastIndex (#16314) (Sosuke Suzuki)

8cc0bbe docs: use more clean link syntax (#16309) (Percy Ma)

6ba269e docs: fix typo (#16288) (jjangga0214)

v8.23.1 - September 12, 2022

b719893 fix: Upgrade eslintrc to stop redefining plugins (#16297) (Brandon Mills)

734b54e fix: improve autofix for the prefer-const rule (#16292) (Nitin Kumar)

6a923ff fix: Ensure that glob patterns are normalized (#16287) (Nicholas C. Zakas)

38e8171 perf: migrate rbTree to js-sdsl (#16267) (Zilong Yao)

16cba3f docs: fix mobile double tap issue (#16293) (Sam Chen)

c6900f8 fix: Ensure globbing doesn't include subdirectories (#16272) (Nicholas C. Zakas)

e098b5f docs: keyboard control to search results (#16222) (Shanmughapriyan S)

1b5b2a7 docs: add Consolas font and prioritize resource loading (#16225) (Amaresh S M)

1c388fb chore: switch nyc to c8 (#16263) (唯然)

67db10c chore: enable linting .eleventy.js again (#16274) (Milos Djermanovic)

1ae8236 docs: copy & use main package version in docs on release (#16252) (Jugal Thakkar)

42bfbd7 chore: fix npm run perf crashes (#16258) (唯然)

279f0af docs: Improve id-denylist documentation (#16223) (Mert Ciflikli)

v8.23.0 - August 26, 2022

2e004ab chore: upgrade @eslint/eslintrc@1.3.1 (#16249) (Milos Djermanovic)

d35fbbe chore: Upgrade to [email protected] (#16243) (Milos Djermanovic)

3e5839e feat: Enable eslint.config.js lookup from CLI (#16235) (Nicholas C. Zakas)

30b1a2d feat: add allowEmptyCase option to no-fallthrough rule (#15887) (Amaresh S M)

ed26229 test: add no-extra-parens tests with rest properties (#16236) (Milos Djermanovic)

deaf69f chore: fix off-by-one min-width: 1023px media queries (#15974) (Milos Djermanovic)

63dec9f refactor: simplify parseListConfig (#16241) (Milos Djermanovic)

43f03aa feat: no-warning-comments support comments with decoration (#16120) (Lachlan Hunt)

b1918da docs: package.json conventions (#16206) (Patrick McElhaney)

0e03c33 docs: remove word immediately (#16217) (Strek)

c6790db docs: add anchor link for "migrating from jscs" (#16207) (Percy Ma)

7137344 docs: auto-generation edit link (#16213) (Percy Ma)

Commits

a578780 8.24.0

f2cfacd Build: changelog update for 8.24.0

131e646 chore: Upgrade @humanwhocodes/config-array for perf (#16339)

2c152ff docs: note false positive Object.getOwnPropertyNames in prefer-reflect (#16...

bf7bd88 docs: fix warn severity description for new config files (#16324)

504fe59 perf: switch from object spread to Object.assign when merging globals (#16311)

1729f9e feat: account for sourceType: "commonjs" in the strict rule (#16308)

b0d72c9 feat: add rule logical-assignment-operators (#16102)

f02bcd9 feat: array-callback-return support findLast and findLastIndex (#16314)

8cc0bbe docs: use more clean link syntax (#16309)

Additional commits viewable in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 2
chore(deps-dev): bump @types/node from 18.7.9 to 18.7.21
Bumps @types/node from 18.7.9 to 18.7.21.

Commits

See full diff in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 2
chore(deps): bump esbuild from 0.15.5 to 0.15.9
Bumps esbuild from 0.15.5 to 0.15.9.

Release notes

Sourced from esbuild's releases.

v0.15.9

Fix an obscure npm package installation issue with --omit=optional (#2558)

The previous release introduced a regression with npm install esbuild --omit=optional where the file node_modules/.bin/esbuild would no longer be present after installation. That could cause any package scripts which used the esbuild command to no longer work. This release fixes the regression so node_modules/.bin/esbuild should now be present again after installation. This regression only affected people installing esbuild using npm with either the --omit=optional or --no-optional flag, which is a somewhat unusual situation.

More details:

The reason for this regression is due to some obscure npm implementation details. Since the Go compiler doesn't support trivial cross-compiling on certain Android platforms, esbuild's installer installs a WebAssembly shim on those platforms instead. In the previous release I attempted to simplify esbuild's WebAssembly shims to depend on the esbuild-wasm package instead of including another whole copy of the WebAssembly binary (to make publishing faster and to save on file system space after installation). However, both the esbuild package and the esbuild-wasm package provide a binary called esbuild and it turns out that adding esbuild-wasm as a nested dependency of the esbuild package (specifically esbuild optionally depends on @esbuild/android-arm which depends on esbuild-wasm) caused npm to be confused about what node_modules/.bin/esbuild is supposed to be.

It's pretty strange and unexpected that disabling the installation of optional dependencies altogether would suddenly cause an optional dependency's dependency to conflict with the top-level package. What happens under the hood is that if --omit=optional is present, npm attempts to uninstall the esbuild-wasm nested dependency at the end of npm install (even though the esbuild-wasm package was never installed due to --omit=optional). This uninstallation causes node_modules/.bin/esbuild to be deleted.

After doing a full investigation, I discovered that npm's handling of the .bin directory is deliberately very brittle. When multiple packages in the dependency tree put something in .bin with the same name, the end result is non-deterministic/random. What you get in .bin might be from one package, from the other package, or might be missing entirely. The workaround suggested by npm is to just avoid having two packages that put something in .bin with the same name. So this was fixed by making the @esbuild/android-arm and esbuild-android-64 packages each include another whole copy of the WebAssembly binary, which works because these packages don't put anything in .bin.

v0.15.8

Fix JSX name collision edge case (#2534)

Code generated by esbuild could have a name collision in the following edge case:

The JSX transformation mode is set to automatic, which causes import statements to be inserted

An element uses a {...spread} followed by a key={...}, which uses the legacy createElement fallback imported from react

Another import uses a name that ends with react such as @remix-run/react

The output format has been set to CommonJS so that import statements are converted into require calls

In this case, esbuild previously generated two variables with the same name import_react, like this:

var import_react = require("react"); var import_react2 = require("@remix-run/react");

That bug is fixed in this release. The code generated by esbuild no longer contains a name collision.

Fall back to WebAssembly on Android ARM (#1556, #1578, #2335, #2526)

Go's compiler supports trivial cross-compiling to almost all platforms without installing any additional software other than the Go compiler itself. This has made it very easy for esbuild to publish native binary executables for many platforms. However, it strangely doesn't support cross-compiling to Android ARM without installing the Android build tools.

So instead of publishing a native esbuild binary executable to npm, this release publishes a WebAssembly fallback build. This is essentially the same as the esbuild-wasm package but it's installed automatically when you install the esbuild package on Android ARM. So packages that depend on the esbuild package should now work on Android ARM. This change has not yet been tested end-to-end because I don't have a 32-bit Android ARM device myself, but in theory it should work.

This inherits the drawbacks of WebAssembly including significantly slower performance than native as well as potentially also more severe memory usage limitations and lack of certain features (e.g. --serve). If you want to use a native binary executable of esbuild on Android ARM, you may be able to build it yourself from source after installing the Android build tools.

Attempt to better support Yarn's ignorePatternData feature (#2495)

Part of resolving paths in a project using Yarn's Plug'n'Play feature involves evaluating a regular expression in the ignorePatternData property of .pnp.data.json. However, it turns out that the particular regular expressions generated by Yarn use some syntax that works with JavaScript regular expressions but that does not work with Go regular expressions.

In this release, esbuild will now strip some of the the problematic syntax from the regular expression before compiling it, which should hopefully allow it to be compiled by Go's regular expression engine. The specific character sequences that esbuild currently strips are as follows:

(?!\.)

(?!(?:^|\/)\.)

(?!\.{1,2}(?:\/|$))

(?!(?:^|\/)\.{1,2}(?:\/|$))

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.15.9

Fix an obscure npm package installation issue with --omit=optional (#2558)

The previous release introduced a regression with npm install esbuild --omit=optional where the file node_modules/.bin/esbuild would no longer be present after installation. That could cause any package scripts which used the esbuild command to no longer work. This release fixes the regression so node_modules/.bin/esbuild should now be present again after installation. This regression only affected people installing esbuild using npm with either the --omit=optional or --no-optional flag, which is a somewhat unusual situation.

More details:

The reason for this regression is due to some obscure npm implementation details. Since the Go compiler doesn't support trivial cross-compiling on certain Android platforms, esbuild's installer installs a WebAssembly shim on those platforms instead. In the previous release I attempted to simplify esbuild's WebAssembly shims to depend on the esbuild-wasm package instead of including another whole copy of the WebAssembly binary (to make publishing faster and to save on file system space after installation). However, both the esbuild package and the esbuild-wasm package provide a binary called esbuild and it turns out that adding esbuild-wasm as a nested dependency of the esbuild package (specifically esbuild optionally depends on @esbuild/android-arm which depends on esbuild-wasm) caused npm to be confused about what node_modules/.bin/esbuild is supposed to be.

It's pretty strange and unexpected that disabling the installation of optional dependencies altogether would suddenly cause an optional dependency's dependency to conflict with the top-level package. What happens under the hood is that if --omit=optional is present, npm attempts to uninstall the esbuild-wasm nested dependency at the end of npm install (even though the esbuild-wasm package was never installed due to --omit=optional). This uninstallation causes node_modules/.bin/esbuild to be deleted.

After doing a full investigation, I discovered that npm's handling of the .bin directory is deliberately very brittle. When multiple packages in the dependency tree put something in .bin with the same name, the end result is non-deterministic/random. What you get in .bin might be from one package, from the other package, or might be missing entirely. The workaround suggested by npm is to just avoid having two packages that put something in .bin with the same name. So this was fixed by making the @esbuild/android-arm and esbuild-android-64 packages each include another whole copy of the WebAssembly binary, which works because these packages don't put anything in .bin.

0.15.8

Fix JSX name collision edge case (#2534)

Code generated by esbuild could have a name collision in the following edge case:

The JSX transformation mode is set to automatic, which causes import statements to be inserted

An element uses a {...spread} followed by a key={...}, which uses the legacy createElement fallback imported from react

Another import uses a name that ends with react such as @remix-run/react

The output format has been set to CommonJS so that import statements are converted into require calls

In this case, esbuild previously generated two variables with the same name import_react, like this:

var import_react = require("react"); var import_react2 = require("@remix-run/react");

That bug is fixed in this release. The code generated by esbuild no longer contains a name collision.

Fall back to WebAssembly on Android ARM (#1556, #1578, #2335, #2526)

Go's compiler supports trivial cross-compiling to almost all platforms without installing any additional software other than the Go compiler itself. This has made it very easy for esbuild to publish native binary executables for many platforms. However, it strangely doesn't support cross-compiling to Android ARM without installing the Android build tools.

So instead of publishing a native esbuild binary executable to npm, this release publishes a WebAssembly fallback build. This is essentially the same as the esbuild-wasm package but it's installed automatically when you install the esbuild package on Android ARM. So packages that depend on the esbuild package should now work on Android ARM. This change has not yet been tested end-to-end because I don't have a 32-bit Android ARM device myself, but in theory it should work.

This inherits the drawbacks of WebAssembly including significantly slower performance than native as well as potentially also more severe memory usage limitations and lack of certain features (e.g. --serve). If you want to use a native binary executable of esbuild on Android ARM, you may be able to build it yourself from source after installing the Android build tools.

Attempt to better support Yarn's ignorePatternData feature (#2495)

Part of resolving paths in a project using Yarn's Plug'n'Play feature involves evaluating a regular expression in the ignorePatternData property of .pnp.data.json. However, it turns out that the particular regular expressions generated by Yarn use some syntax that works with JavaScript regular expressions but that does not work with Go regular expressions.

In this release, esbuild will now strip some of the the problematic syntax from the regular expression before compiling it, which should hopefully allow it to be compiled by Go's regular expression engine. The specific character sequences that esbuild currently strips are as follows:

(?!\.)

(?!(?:^|\/)\.)

... (truncated)

Commits

085265a publish 0.15.9 to npm

f84de90 use a custom message for macOS architecture issues

ba91ed1 makefile: publish four at a time again

e55f980 add validate to clean

02d3ded build all platforms in ci

44c5417 fix android arm package in make clean

eb9de88 additional platform target updates

758d4e1 fix #2558: remove esbuild-wasm package nesting

a333130 update platform targets

8b3bb3b update wasm-napi-exit0 targets

Additional commits viewable in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 2
chore(deps): bump esbuild from 0.15.5 to 0.15.8
Bumps esbuild from 0.15.5 to 0.15.8.

Release notes

Sourced from esbuild's releases.

v0.15.8

Fix JSX name collision edge case (#2534)

Code generated by esbuild could have a name collision in the following edge case:

The JSX transformation mode is set to automatic, which causes import statements to be inserted

An element uses a {...spread} followed by a key={...}, which uses the legacy createElement fallback imported from react

Another import uses a name that ends with react such as @remix-run/react

The output format has been set to CommonJS so that import statements are converted into require calls

In this case, esbuild previously generated two variables with the same name import_react, like this:

var import_react = require("react"); var import_react2 = require("@remix-run/react");

That bug is fixed in this release. The code generated by esbuild no longer contains a name collision.

Fall back to WebAssembly on Android ARM (#1556, #1578, #2335, #2526)

Go's compiler supports trivial cross-compiling to almost all platforms without installing any additional software other than the Go compiler itself. This has made it very easy for esbuild to publish native binary executables for many platforms. However, it strangely doesn't support cross-compiling to Android ARM without installing the Android build tools.

So instead of publishing a native esbuild binary executable to npm, this release publishes a WebAssembly fallback build. This is essentially the same as the esbuild-wasm package but it's installed automatically when you install the esbuild package on Android ARM. So packages that depend on the esbuild package should now work on Android ARM. This change has not yet been tested end-to-end because I don't have a 32-bit Android ARM device myself, but in theory it should work.

This inherits the drawbacks of WebAssembly including significantly slower performance than native as well as potentially also more severe memory usage limitations and lack of certain features (e.g. --serve). If you want to use a native binary executable of esbuild on Android ARM, you may be able to build it yourself from source after installing the Android build tools.

Attempt to better support Yarn's ignorePatternData feature (#2495)

Part of resolving paths in a project using Yarn's Plug'n'Play feature involves evaluating a regular expression in the ignorePatternData property of .pnp.data.json. However, it turns out that the particular regular expressions generated by Yarn use some syntax that works with JavaScript regular expressions but that does not work with Go regular expressions.

In this release, esbuild will now strip some of the the problematic syntax from the regular expression before compiling it, which should hopefully allow it to be compiled by Go's regular expression engine. The specific character sequences that esbuild currently strips are as follows:

(?!\.)

(?!(?:^|\/)\.)

(?!\.{1,2}(?:\/|$))

(?!(?:^|\/)\.{1,2}(?:\/|$))

These seem to be used by Yarn to avoid the . and .. path segments in the middle of relative paths. The removal of these character sequences seems relatively harmless in this case since esbuild shouldn't ever generate such path segments. This change should add support to esbuild for Yarn's pnpIgnorePatterns feature.

Fix non-determinism issue with legacy block-level function declarations and strict mode (#2537)

When function declaration statements are nested inside a block in strict mode, they are supposed to only be available within that block's scope. But in "sloppy mode" (which is what non-strict mode is commonly called), they are supposed to be available within the whole function's scope:

// This returns 1 due to strict mode function test1() { 'use strict' function fn() { return 1 } if (true) { function fn() { return 2 } }

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.15.8

Fix JSX name collision edge case (#2534)

Code generated by esbuild could have a name collision in the following edge case:

The JSX transformation mode is set to automatic, which causes import statements to be inserted

An element uses a {...spread} followed by a key={...}, which uses the legacy createElement fallback imported from react

Another import uses a name that ends with react such as @remix-run/react

The output format has been set to CommonJS so that import statements are converted into require calls

In this case, esbuild previously generated two variables with the same name import_react, like this:

var import_react = require("react"); var import_react2 = require("@remix-run/react");

That bug is fixed in this release. The code generated by esbuild no longer contains a name collision.

Fall back to WebAssembly on Android ARM (#1556, #1578, #2335, #2526)

Go's compiler supports trivial cross-compiling to almost all platforms without installing any additional software other than the Go compiler itself. This has made it very easy for esbuild to publish native binary executables for many platforms. However, it strangely doesn't support cross-compiling to Android ARM without installing the Android build tools.

So instead of publishing a native esbuild binary executable to npm, this release publishes a WebAssembly fallback build. This is essentially the same as the esbuild-wasm package but it's installed automatically when you install the esbuild package on Android ARM. So packages that depend on the esbuild package should now work on Android ARM. This change has not yet been tested end-to-end because I don't have a 32-bit Android ARM device myself, but in theory it should work.

This inherits the drawbacks of WebAssembly including significantly slower performance than native as well as potentially also more severe memory usage limitations and lack of certain features (e.g. --serve). If you want to use a native binary executable of esbuild on Android ARM, you may be able to build it yourself from source after installing the Android build tools.

Attempt to better support Yarn's ignorePatternData feature (#2495)

Part of resolving paths in a project using Yarn's Plug'n'Play feature involves evaluating a regular expression in the ignorePatternData property of .pnp.data.json. However, it turns out that the particular regular expressions generated by Yarn use some syntax that works with JavaScript regular expressions but that does not work with Go regular expressions.

In this release, esbuild will now strip some of the the problematic syntax from the regular expression before compiling it, which should hopefully allow it to be compiled by Go's regular expression engine. The specific character sequences that esbuild currently strips are as follows:

(?!\.)

(?!(?:^|\/)\.)

(?!\.{1,2}(?:\/|$))

(?!(?:^|\/)\.{1,2}(?:\/|$))

These seem to be used by Yarn to avoid the . and .. path segments in the middle of relative paths. The removal of these character sequences seems relatively harmless in this case since esbuild shouldn't ever generate such path segments. This change should add support to esbuild for Yarn's pnpIgnorePatterns feature.

Fix non-determinism issue with legacy block-level function declarations and strict mode (#2537)

When function declaration statements are nested inside a block in strict mode, they are supposed to only be available within that block's scope. But in "sloppy mode" (which is what non-strict mode is commonly called), they are supposed to be available within the whole function's scope:

// This returns 1 due to strict mode function test1() { 'use strict' function fn() { return 1 }

... (truncated)

Commits

7553dbe publish 0.15.8 to npm

d65315a Add JSX side effects option (#2546)

a6acbaa minify static object spread in jsx props

c9b24d8 fix #2555: parse @keyframes with string namems

93e068d fix #2557: remove warning about top-level this

be4e272 fix #2541: split changelog by year

3e2374c fix #2537: sort map keys to fix non-determinism

112a033 turn 64bit android package into a simple shim

a849b7a add missing file to make clean

a18c9fa fix #2495: strip non-go ignorePatternData stuff

Additional commits viewable in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 2
chore(deps-dev): bump @unvented/empty from 1.0.3 to 1.0.4
Bumps @unvented/empty from 1.0.3 to 1.0.4.

Release notes

Sourced from @unvented/empty's releases.

v1.0.4

Changes

bump dependencies (once a month)

Changelog

Sourced from @unvented/empty's changelog.

v1.0.4

Changes

bump dependencies (once a month)

Commits

927150c chore: bump dependencies (once a month)

7aba394 chore(deps-dev): bump @types/node from 18.7.15 to 18.7.17 (#30)

5a8288e chore(deps-dev): bump eslint from 8.23.0 to 8.23.1 (#29)

5011e30 chore(deps-dev): bump typescript from 4.8.2 to 4.8.3 (#28)

8bf58c2 chore(deps-dev): bump esbuild from 0.15.5 to 0.15.7 (#26)

09c3129 chore(deps-dev): bump @types/node from 18.7.13 to 18.7.15 (#25)

d771fc6 chore(deps-dev): bump eslint from 8.22.0 to 8.23.0 (#22)

d5b2efc chore(deps-dev): bump typescript from 4.7.4 to 4.8.2 (#21)

5b3e76e chore(deps-dev): bump @types/node from 18.7.11 to 18.7.13 (#20)

7f465db chore(deps-dev): bump @azury/eslint-config from 1.0.6 to 1.0.7 (#19)

Additional commits viewable in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 2
chore(deps-dev): bump @types/node from 18.8.0 to 18.8.2
Bumps @types/node from 18.8.0 to 18.8.2.

Commits

See full diff in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 0
chore(deps-dev): bump @unvented/empty from 1.0.4 to 1.1.0
Bumps @unvented/empty from 1.0.4 to 1.1.0.

Release notes

Sourced from @unvented/empty's releases.

v1.1.0

New Features

add JavaScript API

Changes

update website and email

Changelog

Sourced from @unvented/empty's changelog.

v1.1.0

New Features

add JavaScript API

Changes

update website and email

Commits

0fab3e4 chore: bump package to v1.1.0

9314240 refactor: remove lint workflow

406547b feat: add js api

650bf16 docs: update readme

6f28cb9 refactor: disable git-tag-version for npm

190c866 chore(deps-dev): bump @types/node from 18.7.23 to 18.8.0 (#39)

4e5facb chore(deps-dev): bump esbuild from 0.15.9 to 0.15.10 (#38)

3bb9d45 chore(deps-dev): bump @types/node from 18.7.18 to 18.7.23 (#37)

59382a9 chore(deps-dev): bump typescript from 4.8.3 to 4.8.4 (#36)

a997aad chore(deps-dev): bump eslint from 8.23.1 to 8.24.0 (#35)

Additional commits viewable in compare view

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.

Dependabot commands and options

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)

dependencies
opened by dependabot[bot] 0
ci: version packages
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to dev, this PR will be updated.

Releases

@darkflare/[email protected]

Major Changes

#38 3836ac6 Thanks @unvented! - refactor!: rename generateConfig method to generate

#36 0b712ca Thanks @unvented! - refactor!: rename defineConfig method to define

#39 23e31ce Thanks @unvented! - refactor!: rename parseConfig method to parse

Patch Changes

#43 801de8c Thanks @unvented! - refactor: migrate to azury's style guide

e242180 Thanks @unvented! - refactor: replace rimraf with @unvented/empty
opened by github-actions[bot] 0

Releases(v0.4.3)

v0.4.3(Jul 27, 2022)
Patch Changes

#33 5f25636 Thanks @unvented! - docs: add contact section to readme

Source code(tar.gz)
Source code(zip)
v0.4.2(Jul 25, 2022)
Patch Changes

#29 f106363 Thanks @unvented! - test: fix config loaded via extends option

#28 4528f58 Thanks @unvented! - fix: spacing after route option in output file

#26 56c9884 Thanks @unvented! - feat: add support for .jsonc files

Add support for .jsonc files, aka. json files with comments.

Source code(tar.gz)
Source code(zip)
v0.4.1(Jul 24, 2022)
Patch Changes

#21 c2c08a2 Thanks @unvented! - chore: move repo to darkflarengine org

Move wjson to the darkflarengine organization, since it was mainly developed for darkflare.

Source code(tar.gz)
Source code(zip)
v0.4.0(Jul 22, 2022)
Minor Changes

#17 52b884e Thanks @unvented! - refactor!: move env related config under env key

Move all environment-related settings under the env key to avoid confusion.

Source code(tar.gz)
Source code(zip)
v0.3.1(Jul 11, 2022)
Patch Changes

#6 c7aa4c1 Thanks @unvented! - feat: add basic error logging

Print errors to the console.

#8 e0d6bbc Thanks @unvented! - refactor: exclude cli from typescript compilation

Exclude CLI file from TypeScript compilation to reduce package size. No change for users since the code is internal anyway.

Source code(tar.gz)
Source code(zip)
v0.3.0(Jul 8, 2022)
Breaking Changes

#3 - refactor!: raise required node version

Need to raise the required node version in engines field to v18 due to new extends option.

New Features

#2 - feat: add extends option

Extend your configuration with an external configuration. This functionality has an infinite depth. Currently, only JSON file imports via HTTP/HTTPS are supported.

{ "extends": "https://example.com/other_config.json", // overwrite the options of the config you're extending or add other options }

#4 - feat: add yaml support

Add support for wrangler.yaml and wrangler.yml files.

Source code(tar.gz)
Source code(zip)
v0.2.0(Jul 7, 2022)
Breaking Changes

renamed package to @darkflare/wjson

Bug Fixes

added missing #!/usr/bin/env node to the start of the bin file

Source code(tar.gz)
Source code(zip)
v0.1.1(Jul 7, 2022)
Features

added npmignore

Bug Fixes

fixed invalid cli command name for package

Source code(tar.gz)
Source code(zip)