Installations
npm install @morgul/snowpack-plugin-vue2
Developer Guide
Typescript
No
Module System
CommonJS
Node Version
14.16.0
NPM Version
7.16.0
Releases
Contributors
Unable to fetch Contributors
Languages
JavaScript (81.07%)
Vue (14.94%)
HTML (2.18%)
TypeScript (1.81%)
Love this project? Help keep it running — sponsor us today! 🚀
Developer
Morgul
Download Statistics
Total Downloads
23,996
Last Day
2
Last Week
27
Last Month
146
Last Year
3,187
GitHub Statistics
MIT License
6 Stars
21 Commits
2 Forks
3 Watchers
1 Branches
2 Contributors
Updated on Mar 16, 2022
Package Meta Information
Latest Version
0.4.2
Package Id
@morgul/snowpack-plugin-vue2@0.4.2
Unpacked Size
41.21 kB
Size
10.99 kB
File Count
33
NPM Version
7.16.0
Node Version
14.16.0
Total Downloads
Cumulative downloads
Total Downloads
23,996
Last Day
-33.3%
2
Compared to previous day
Last Week
-3.6%
27
Compared to previous week
Last Month
-22.3%
146
Compared to previous month
Last Year
-28.5%
3,187
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dev Dependencies
1
Snowpack Vue 2 Plugin
This is a snowpack plugin for Vue v2.X, based off of the official Vue v3 plugin, @snowpack/plugin-vue. The primary goal of this plugin is to provide an 'adapter' layer for @vue/component-compiler-utils and vue-template-compiler to reuse as much of the official snowpack vue plugin as possible. With that goal in mind, this repo is set up with /plugin
corresponding to a copy of the /plugins/plugin-vue
code, so that should there ever be interest in making snowpack work with Vue2, the effort to port my changes to the vue plugin is minimal.
Why Vue 2?
Currently, even https://vuejs.org/ points to the v2.x documentation. It's not that Vue 3 is bad, by any means. It will eventually, take over as the leading version of Vue. The problem is, most libraries haven't updated yet, including a lot of the popular front-end frameworks. They won't have alpha versions for several more months, and probably won't have production versions till year's end. And those are just the popular, large projects. As a developer of dozens of Vue sites, I doubt I'll have my projects converted for at least a year, if not two.
I don't know about you, but I don't see why I should have to wait to start using Snowpack.
Usage
Simply install the plugin:
npm
:
1$ npm install -D @morgul/snowpack-plugin-vue2
yarn
:
1$ yarn add -D @morgul/snowpack-plugin-vue2
Then, add it to your snowpack.config.js
:
1// snowpack.config.json 2{ 3 "plugins": [ 4 "@morgul/snowpack-plugin-vue2" 5 ] 6}
Development
This plugin is definitely me scratching my own itch. And I haven't even decided if I like snowpack yet. But there's a need, and while there's about three or four vue2 plugins... none of them worked when I tried. So, here's a more formal engineered solution.
Vue Library choice
Digging through the source code to vue-loader, I came upon @vue/component-compiler-utils, which appears to have been created after @vue/compiler-sfc, with the same API, as a way of centralizing the code for doing all of this. I agree that something like @vue/compiler-sfc is required, but that's Vue 3 only, so I'm glad they backported that design to Vue2. It makes my life significantly easier.
Note: As more development has happened, it's become clear that @vue/component-compiler-utils doesn't do everything that @vue/compiler-sfc, instead relying on vue-loader to do some of it. That's fine, we can slowly intriduce vue-loader code as needed to handle these edge cases.
Project Guidelines
These are the guidelines for working on this project.
- Absolutely no modifications to @vue/component-compiler-utils or vue-template-compiler.
- Minimal to no modifications to @snowpack/plugin-vue.
- All adaption code must live in
/compiler
. - All plugin code must live in
/plugin
. - Where possible, external packages are used without modification, only adaptation.
Project layout
The bulk of this project's code lives in /compiler
. The /plugin
is a verbatim copy of @snowpack/plugin-vue, with as few changes as possible. (Even the original package.json
is kept around.) There is also a sample project contained in /example
, to act as both a test for the plugin, and a usage guide.

No vulnerabilities found.
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
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 1/19 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
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
project is not fuzzed
Details
- Warn: no fuzzer integrations found
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 3 are checked with a SAST tool
Reason
30 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-67mh-4wv8-2f99
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-5j4c-8p2g-v4jx
- Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
- Warn: Project is vulnerable to: GHSA-93q8-gq69-wqmw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-w573-4hg7-7wgq
- Warn: Project is vulnerable to: GHSA-ww39-953v-wcq6
- Warn: Project is vulnerable to: GHSA-43f8-2h32-f4cj
- Warn: Project is vulnerable to: GHSA-896r-f27r-55mw
- Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
- Warn: Project is vulnerable to: GHSA-29mw-wpgm-hmr9
- Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-xvch-5gv4-984h
- Warn: Project is vulnerable to: GHSA-hj48-42vr-x3v9
- Warn: Project is vulnerable to: GHSA-566m-qj78-rww5
- Warn: Project is vulnerable to: GHSA-hwj9-h5mp-3pm3
- Warn: Project is vulnerable to: GHSA-7fh5-64p2-3v2j
- Warn: Project is vulnerable to: GHSA-hrpp-h998-j3pp
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-jgrx-mgxx-jf9v
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-g3ch-rx76-35fx
- Warn: Project is vulnerable to: GHSA-j8xg-fqg3-53r7
- Warn: Project is vulnerable to: GHSA-6fc8-4gx4-v693
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
Score
1.7
/10
Last Scanned on 2025-02-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