Installations
npm install @pognetwork/vite-plugin-wasm-pack
Developer Guide
Typescript
Yes
Module System
CommonJS
Node Version
16.11.0
NPM Version
8.0.0
Score
69.3
Supply Chain
98.2
Quality
75.3
Maintenance
100
Vulnerability
100
License
Releases
Contributors
Unable to fetch Contributors
Languages
TypeScript (80.39%)
Rust (9.92%)
HTML (9.69%)
validate.email 🚀
Verify real, reachable, and deliverable emails with instant MX records, SMTP checks, and disposable email detection.
Developer
nshen
Download Statistics
Total Downloads
502
Last Day
1
Last Week
1
Last Month
12
Last Year
80
GitHub Statistics
MIT License
248 Stars
56 Commits
37 Forks
3 Watchers
1 Branches
6 Contributors
Updated on Mar 10, 2025
Bundle Size
56.94 kB
Minified
18.32 kB
Minified + Gzipped
Package Meta Information
Latest Version
0.1.8
Package Id
@pognetwork/vite-plugin-wasm-pack@0.1.8
Unpacked Size
13.02 kB
Size
4.32 kB
File Count
5
NPM Version
8.0.0
Node Version
16.11.0
Total Downloads
Cumulative downloads
Total Downloads
502
Last Day
0%
1
Compared to previous day
Last Week
0%
1
Compared to previous week
Last Month
9.1%
12
Compared to previous month
Last Year
-25.2%
80
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dev Dependencies
6
🦀 Vite plugin for rust wasm-pack, it's simple.
Quick start
Make sure wasm-pack installed correctly.
Clone this repo or download the zip file, extract the example folder.
example
|
|-- my-crate # rust project folder, there is a Cargo.toml in it
|-- src # front end source code
| |-- index.ts # entry point
|-- index.html # html entry
|-- vite.config.ts # vite config file
|__ package.json # npm config file
Install npm develop dependencies, in example folder run:
1yarn install 2# or 3# npm install
After that you can build rust project
to WebAassembly
by using wasm-pack
.
1wasm-pack build ./my-crate --target web
Now the my-crate
module is ready, start vite dev server.
1yarn dev 2or 3#npm run dev
Done, if below is showing.
1 vite v2.6.5 dev server running at: 2 3 > Local: http://localhost:3000/ 4 5 ready in 169ms.
Install manually
1yarn add vite vite-plugin-wasm-pack -D 2# or 3# npm i vite vite-plugin-wasm-pack vite -D
Usage
Add this plugin to vite.config.ts
1import { defineConfig } from 'vite';
2import wasmPack from 'vite-plugin-wasm-pack';
3
4export default defineConfig({
5 // pass your local crate path to the plugin
6 plugins: [wasmPack('./my-crate')]
7});
Add script to package.json
1"scripts": { 2 "dev": "vite", 3 "build": "vite build" 4}
âš Don't forget to build your wasm-pack crate first!
1wasm-pack build ./my-crate --target web
Tips: you can add a wasm
script to package.json
like this:
1"scripts": { 2 "wasm": "wasm-pack build ./my-crate --target web", 3 "dev": "yarn wasm && vite", 4 "build": "vite build" 5}
Then, run:
1yarn dev
This will start dev server, and install my-crate
that you built earlier.
Use wasm-pack package installed via npm
If you want use a package from npm that built with wasm-pack, like this one test-npm-crate
you have to pass the package name to the second param of our plugin.
wasmPack(['./my-local-crate'],['test-npm-crate'])
full example is in ./npm-crate-example folder.
Examples
License
MIT, see the license file

No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
Found 5/23 approved changesets -- score normalized to 2
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/publish-to-npm.yml:1
- Info: no jobLevel write permissions found
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-to-npm.yml:10: update your workflow using https://app.stepsecurity.io/secureworkflow/nshen/vite-plugin-wasm-pack/publish-to-npm.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-to-npm.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/nshen/vite-plugin-wasm-pack/publish-to-npm.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/publish-to-npm.yml:18
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 12 are checked with a SAST tool
Reason
11 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: RUSTSEC-2022-0078 / GHSA-f85w-wvc7-crwc
- Warn: Project is vulnerable to: RUSTSEC-2022-0054 / GHSA-rc23-xxgq-x27g
- Warn: Project is vulnerable to: GHSA-67mh-4wv8-2f99
- Warn: Project is vulnerable to: GHSA-mwcw-c2x4-8c55
- Warn: Project is vulnerable to: GHSA-7fh5-64p2-3v2j
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-mv48-hcvh-8jj8
- Warn: Project is vulnerable to: GHSA-353f-5xf4-qw67
- Warn: Project is vulnerable to: GHSA-64vr-g452-qvp3
- Warn: Project is vulnerable to: GHSA-9cwx-2883-4wfx
- Warn: Project is vulnerable to: GHSA-vg6x-rcgg-rjx6
Score
2.7
/10
Last Scanned on 2025-03-10
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More