vite-plugin-electron-renderer
Advanced tools
Comparing version 0.4.0 to 0.4.1
@@ -26,3 +26,6 @@ const fs = require('fs'); | ||
// Resolve package.json dependencies | ||
const pkgId = path.join(config.root, 'package.json'); | ||
let pkgId = path.join(config.root, 'package.json'); | ||
if (!fs.existsSync(pkgId)) { | ||
pkgId = path.join(process.cwd(), 'package.json'); | ||
} | ||
if (fs.existsSync(pkgId)) { | ||
@@ -29,0 +32,0 @@ const pkg = require(pkgId); |
{ | ||
"name": "vite-plugin-electron-renderer", | ||
"version": "0.4.0", | ||
"version": "0.4.1", | ||
"description": "Support use Node.js API in Electron-Renderer", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
@@ -52,2 +52,36 @@ # vite-plugin-electron-renderer | ||
## dependencies vs devDependencies | ||
The simplest way | ||
- Node.js package in `dependencies` of `package.josn` | ||
- Web package in `devDependencies` of `package.josn` | ||
In general, Vite may not be able to correctly build Node.js packages, especially C/C++ native modules, but Vite can load them as external packages. | ||
*通常的,Vite 可能不能正确的构建 Node.js 的包,尤其是 C/C++ 原生模块,但是 Vite 可以将它们以外部包的形式加载。* | ||
e.g. | ||
Electron-Main | ||
```js | ||
import { ipcMain } from 'electron' | ||
↓ | ||
const { ipcMain } = require('electron') | ||
``` | ||
Electron-Renderer | ||
```js | ||
import { ipcRenderer } from 'electron' | ||
↓ | ||
// Generate a virtual module by vite-plugin-reaolve | ||
const electron = require('electron') | ||
export const ipcRenderer = electron.ipcRenderer | ||
↓ | ||
// The following code snippet will work in Electron-Renderer, | ||
// and it doesn't seem to have changed :) | ||
import { ipcRenderer } from 'electron' | ||
``` | ||
## How to work | ||
@@ -54,0 +88,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
13938
240
115
0