logseq-plugin-heatmap icon indicating copy to clipboard operation
logseq-plugin-heatmap copied to clipboard

Published 20 hours ago • verified publisher icon pengx17

chore(deps): update dependency vite to v3

Open renovate[bot] opened this issue 1 year ago • 1 comments

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) 2.9.15 -> 3.1.2 age adoption passing confidence

Release Notes

vitejs/vite

v3.1.2

Compare Source

v3.1.1

Compare Source

v3.1.0

Compare Source

Main Changes
  • Vite now uses parse5, which parses HTML in the same way as the latest browser versions. This migration gives us a more robust HTML story moving forward (#​9678).
  • Vite now supports using objects as hooks to change execution order (#​9634). Check out the RFC and the implementation upstream at rollup/rollup#​4600 for details and rationale. 
      import { resolve } from 'node:path';
  import { readdir } from 'node:fs/promises';

  export default function getFilesOnDisk() {
    return {
      name: 'getFilesOnDisk',
      writeBundle: {
        // run this hook sequentially even if the hook is parallel
        sequential: true,
        // push this hook to the 'post' stage, after all normal hooks
        order: 'post',
        // hook implementation
        async handler({ dir }) {
          const topLevelFiles = await readdir(resolve(dir))
          console.log(topLevelFiles)
        }
      }
    }
  }
    Read the updated Rollup Plugin docs for more information.

Note After Vite 3.1, you are no longer going to see [vite] hot updated log messages in the browser console. These messages have been moved to the debug channel (#​8855). Check your browser docs to show debug logs.

Features
Bug Fixes
Previous Changelogs
3.1.0-beta.2 (2022-09-02)

See 3.1.0-beta.2 changelog

3.1.0-beta.1 (2022-08-29)

See 3.1.0-beta.1 changelog

3.1.0-beta.0 (2022-08-25)

See 3.1.0-beta.0 changelog

v3.0.9

Compare Source

v3.0.8

Compare Source

v3.0.7

Compare Source

v3.0.6

Compare Source

v3.0.5

Compare Source

v3.0.4

Compare Source

v3.0.3

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

Main Changes

Vite 3 is out! Read the Vite 3 Announcement blog post

  • New docs theme using VitePress v1 alpha: https://vitejs.dev
  • Vite CLI
    • The default dev server port is now 5173, with the preview server starting at 4173.
    • The default dev server host is now localhost instead of 127.0.0.1.
  • Compatibility
    • Vite no longer supports Node v12, which reached its EOL. Node 14.18+ is now required.
    • Vite is now published as ESM, with a CJS proxy to the ESM entry for compatibility.
    • The Modern Browser Baseline now targets browsers which support the native ES Modules and native ESM dynamic import and import.meta.
    • JS file extensions in SSR and lib mode now use a valid extension (js, mjs, or cjs) for output JS entries and chunks based on their format and the package type.
  • Architecture changes
    • Vite now avoids full reload during cold start when imports are injected by plugins in while crawling the initial statically imported modules (#​8869).
    • Vite uses ESM for the SSR build by default, and previous SSR externalization heuristics are no longer needed.
  • import.meta.glob has been improved, read about the new features in the Glob Import Guide
  • The WebAssembly import API has been revised to avoid collisions with future standards. Read more in the WebAssembly guide
  • Improved support for relative base.
  • Experimental Features
  • Bundle size reduction
    • Terser is now an optional dependency. If you use build.minify: 'terser', you'll need to install it (npm add -D terser)
    • node-forge moved out of the monorepo to @​vitejs/plugin-basic-ssl
  • Options that were already deprecated in v2 have been removed.

Note Before updating, check out the migration guide from v2

Features

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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.

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

  • [ ] If you want to rebase/retry this PR, click this checkbox.

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

renovate[bot] avatar Jul 13 '22 16:07 renovate[bot]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
installing v2 tool node v16.16.0
linking tool node v16.16.0
node: v16.16.0 /usr/local/bin/node
npm: 8.11.0  /usr/local/bin/npm
Installed v2 /usr/local/buildpack/tools/v2/node.sh in 7 seconds
installing v2 tool pnpm v7.9.0
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

added 1 package in 2s
linking tool pnpm v7.9.0
7.9.0
Installed v2 /usr/local/buildpack/tools/v2/pnpm.sh in 4 seconds
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 14, reused 0, downloaded 0, added 0
Progress: resolved 22, reused 0, downloaded 0, added 0
Progress: resolved 25, reused 0, downloaded 9, added 0
Progress: resolved 26, reused 0, downloaded 17, added 0
Progress: resolved 27, reused 0, downloaded 20, added 0
Progress: resolved 28, reused 0, downloaded 22, added 0
Progress: resolved 28, reused 0, downloaded 23, added 0
Progress: resolved 28, reused 0, downloaded 24, added 0
Progress: resolved 28, reused 0, downloaded 27, added 0
Progress: resolved 29, reused 0, downloaded 28, added 0
Progress: resolved 30, reused 0, downloaded 28, added 0
Progress: resolved 59, reused 0, downloaded 33, added 0
Progress: resolved 72, reused 0, downloaded 48, added 0
Progress: resolved 80, reused 0, downloaded 56, added 0
Progress: resolved 87, reused 0, downloaded 64, added 0
Progress: resolved 92, reused 0, downloaded 73, added 0
Progress: resolved 105, reused 0, downloaded 95, added 0
Progress: resolved 124, reused 0, downloaded 108, added 0
Progress: resolved 133, reused 0, downloaded 116, added 0
Progress: resolved 160, reused 0, downloaded 136, added 0
Progress: resolved 181, reused 0, downloaded 151, added 0
Progress: resolved 196, reused 0, downloaded 165, added 0
Progress: resolved 206, reused 0, downloaded 177, added 0
Progress: resolved 235, reused 0, downloaded 188, added 0
Progress: resolved 267, reused 0, downloaded 216, added 0
Progress: resolved 293, reused 0, downloaded 233, added 0
Progress: resolved 322, reused 0, downloaded 263, added 0
Progress: resolved 339, reused 0, downloaded 285, added 0
Progress: resolved 354, reused 0, downloaded 294, added 0
Progress: resolved 391, reused 0, downloaded 326, added 0
Progress: resolved 414, reused 0, downloaded 348, added 0
Progress: resolved 438, reused 0, downloaded 371, added 0
Progress: resolved 465, reused 0, downloaded 396, added 0
Progress: resolved 491, reused 0, downloaded 420, added 0
Progress: resolved 513, reused 0, downloaded 449, added 0
Progress: resolved 537, reused 0, downloaded 484, added 0
Progress: resolved 547, reused 0, downloaded 512, added 0
Progress: resolved 550, reused 0, downloaded 519, added 0
Progress: resolved 560, reused 0, downloaded 537, added 0
Progress: resolved 560, reused 0, downloaded 538, added 0
Progress: resolved 577, reused 0, downloaded 553, added 0
Progress: resolved 577, reused 0, downloaded 555, added 0
Progress: resolved 577, reused 0, downloaded 556, added 0
undefined
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

.
└─┬ react-calendar-heatmap 1.8.1
  └── ✕ unmet peer react@"^0.14.0 || ^15.0.0 || ^16.0.0": found 18.1.0

hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.

renovate[bot] avatar Jul 13 '22 16:07 renovate[bot]

Socket Security Pull Request Report

👍 No new dependency issues detected in pull request

Pull request report summary
Issue Status
Install scripts ✅ 0 issues
Native code ✅ 0 issues
Bin script confusion ✅ 0 issues
Bin script shell injection ✅ 0 issues
Unresolved require ✅ 0 issues
Invalid package.json ✅ 0 issues
HTTP dependency ✅ 0 issues
Git dependency ✅ 0 issues
Potential typo squat ✅ 0 issues
Known Malware ✅ 0 issues
Telemetry ✅ 0 issues
Protestware/Troll package ✅ 0 issues
Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] [email protected]

⚠️ Please accept the latest app permissions to ensure bot commands work properly. Accept the new permissions here.

Powered by socket.dev

socket-security[bot] avatar Oct 06 '22 16:10 socket-security[bot]