chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nuxt/types	2.14.7 -> 2.14.9
esbuild	^0.8.17 -> ^0.8.19
eslint (source)	7.14.0 -> 7.15.0
eslint-plugin-prettier	3.1.4 -> 3.2.0
nuxt	2.14.7 -> 2.14.9
rollup (source)	^2.34.0 -> ^2.34.1

---

Release Notes

nuxt/nuxt.js

v2.14.9

Compare Source

🍖 Hot Fixes

• #​8421 Only encode non dynamic path params

v2.14.8

Compare Source

🐛 Bug Fixes

• webpack
  • #​8205 Allow transpiling packages in nested node_modules
• general
  • #​8325 Handle route encodings and update vue-router
• vue-router
  • #​8394 Force chidren to be required if default child is present (resolves #​7823)
• cli
  • #​8398 Respect router.trailingSlash when serving static files (resolves #​8350)
  • #​8337 Handle generate.cache.ignore as a function in ensureBuild
• generator
  • #​8237 Nested route missing trailingSlash (resolves #​8165)
  • #​8344 Respect publicPath for static assets (resolves #​7923, #​7815)
• csp
  • #​8352 Apply right csp header when status code is 304 (resolves #​8353)
• vue-app
  • #​8314 Handle missing payloads on full static (resolves #​7717)
  • #​8348 Warn if promises and functions are in fetch state (resolves #​8338)
  • #​8225 TriggerScroll when transitions is disabled
  • #​8289 Use nuxt globalName correctly in nuxt-link and fetch mixin (resolves #​8118)
  • #​8280 Prevent redirection loop with URI-encoded path (resolves #​8116)
• types
  • #​8362 Correct vue.config types
  • #​8349 Add missing isFetching and nbFetching to NuxtApp interface
  • #​8319 NuxtOptionsHead can be a function
  • #​8302 Add missing ssrContext and next typings to Context (resolves #​8296)
• server
  • #​8313 Redirect if router.base specified in development

💅 Refactors

• general
  • #​8210 Use nuxt everywhere
• cli
  • #​8219 Grammatical errors (resolves #​8217)

👓 Tests

• general
  • #​8282 Fix redirect tests

💖 Thanks to

• Ahad Birang (@​farnabaz)
• Audrius Jakumavicius (@​aj-dev)
• Cain Hall (@​cain)
• Daniel Roe (@​danielroe)
• Mathieu TUDISCO (@​mathieutu)
• Orkhan Alikhanov (@​OrkhanAlikhanov)
• Steve Perkins (@​steveperkins)
• @​Zuckjet
• @​padinko

evanw/esbuild

v0.8.19

Compare Source

• Handle non-ambiguous multi-path re-exports (#​568)

  Wildcard re-exports using the export * from 'path' syntax can potentially result in name collisions that cause an export name to be ambiguous. For example, the following code would result in an ambiguous export if both a.js and b.js export a symbol with the same name:

  export * from './a.js'
  export * from './b.js'

  Ambiguous exports have two consequences. First, any ambiguous names are silently excluded from the set of exported names. If you use an import * as wildcard import, the excluded names will not be present. Second, attempting to explicitly import an ambiguous name using an import {} from import clause will result in a module instantiation error.

  This release fixes a bug where esbuild could in certain cases consider a name ambiguous when it actually isn't. Specifically this happens with longer chains of mixed wildcard and named re-exports. Here is one such case:

  // entry.js
  import {x, y} from './not-ambiguous.js'
  console.log(x, y)

  // /not-ambiguous.js
  export * from './a.js'
  export * from './b.js'

  // /a.js
  export * from './c.js'

  // /b.js
  export {x} from './c.js'

  // /c.js
  export let x = 1, y = 2

  Previously bundling entry.js with esbuild would incorrectly generate an error about an ambiguous x export. Now this case builds successfully without an error.

• Omit warnings about non-string paths in await import() inside a try block (#​574)

  Bundling code that uses require() or import() with a non-string path currently generates a warning, because the target of that import will not be included in the bundle. This is helpful to warn about because other bundlers handle this case differently (e.g. Webpack bundles the entire directory tree and emulates a file system lookup) so existing code may expect the target of the import to be bundled.

  You can avoid the warning with esbuild by surrounding the call to require() with a try block. The thinking is that if there is a surrounding try block, presumably the code is expecting the require() call to possibly fail and is prepared to handle the error. However, there is currently no way to avoid the warning for import() expressions. This release introduces an analogous behavior for import() expressions. You can now avoid the warning with esbuild if you use await import() and surround it with a try block.

v0.8.18

Compare Source

• Fix a bug with certain complex optional chains (#​573)

  The ?. optional chaining operator only runs the right side of the operator if the left side is undefined, otherwise it returns undefined. This operator can be applied to both property accesses and function calls, and these can be combined into long chains of operators. These expressions must be transformed to a chain of ?: operators if the ?. operator isn't supported in the configured target environment. However, esbuild had a bug where an optional call of an optional property with a further property access afterward didn't preserve the value of this for the call. This bug has been fixed.

• Fix a renaming bug with external imports

  There was a possibility of a cross-module name collision while bundling in a certain edge case. Specifically, when multiple files both contained an import statement to an external module and then both of those files were imported using require. For example:

  // index.js
  console.log(require('./a.js'), require('./b.js'))

  // a.js
  export {exists} from 'fs'

  // b.js
  export {exists} from 'fs'

  In this case the files a.js and b.js are converted to CommonJS format so they can be imported using require:

  // a.js
  import {exists} from "fs";
  var require_a = __commonJS((exports) => {
    __export(exports, {
      exists: () => exists
    });
  });
  
  // b.js
  import {exists} from "fs";
  var require_b = __commonJS((exports) => {
    __export(exports, {
      exists: () => exists
    });
  });
  
  // index.js
  console.log(require_a(), require_b());

  However, the exists symbol has been duplicated without being renamed. This is will result in a syntax error at run-time. The reason this happens is that the statements in the files a.js and b.js are placed in a nested scope because they are inside the CommonJS closure. The import statements were extracted outside the closure but the symbols they declared were incorrectly not added to the outer scope. This problem has been fixed, and this edge case should no longer result in name collisions.

eslint/eslint

v7.15.0

Compare Source

• 5c11aab Upgrade: @​eslint/esintrc and espree for bug fixes (refs #​13878) (#​13908) (Brandon Mills)
• 0eb7957 Upgrade: file-entry-cache@6.0.0 (#​13877) (Rouven Weßling)
• 683ad00 New: no-unsafe-optional-chaining rule (fixes #​13431) (#​13859) (YeonJuan)
• cbc57fb Fix: one-var autofixing for export (fixes #​13834) (#​13891) (Anix)
• 110cf96 Docs: Fix a broken link in working-with-rules.md (#​13875) (Anton Niklasson)

prettier/eslint-plugin-prettier

v3.2.0

Compare Source

• Skip CI for eslint 6 + node 8 (#​364) (f8f08e4)
• Turn off problematic rules in recommended config (prepare for next eslint-config-prettier version) (#​360) (a1e5591)
• Create dependabot.yml (f58b6c7)
• docs(README): fix prettier getFileInfo link (#​335) (5a690f1)
• build(deps-dev): bump eslint-plugin-eslint-plugin from 2.2.2 to 2.3.0 (8614c45)
• build(deps-dev): bump eslint from 7.3.0 to 7.3.1 (12d9ed8)
• build(deps-dev): bump eslint from 7.2.0 to 7.3.0 (5a6f42e)
• chore: update CI badge in readme (5012b66)
• Use Github Actions for CI (#​305) (41eb64f)

rollup/rollup

v2.34.1

Compare Source

2020-12-03

Bug Fixes

• Avoid Node deprecation warning by using a pattern export for nested Rollup files (#​3896)

Pull Requests

• #​3887: Run memory leak test on all systems (@​lukastaegert)
• #​3892: Add pull_request to windows github actions (@​shellscape)
• #​3893: Update dependencies (@​lukastaegert)
• #​3896: Replace deprecated folder package export with pattern export (@​lukastaegert)

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

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

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

---

• If you want to rebase/retry this PR, check this box

---

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