Vue Cli Plugin Vite: Use Vite today, with Vue-cli.

Use Vite Today

out-of-the-box for vue-cli projects without any codebase modifications.

demo/boilerplate

Usage

# 1. first step
vue add vite

# 2. second step
# NOTE you cannot directly use `vite` or `npx vite` since it is origin vite not this plugin.
yarn vite // or npm run vite

# 3. add optimizeDeps#include (optional and will speedup devServer start time a lot)
# added in vue.config.js#pluginOptions.vite.optimizeDeps.include
# e.g.: ['vue', 'vue-router', 'vuex']
# all scanned deps(logged in terminal) can be added for speedup.

Motivation

• We have lots of exists vue-cli(3.x / 4.x) projects.
• In Production: vue-cli based on webpack is still the best practice for bundling webapp(with code spliting, legecy-build for old browsers).
• In Development: instant server start and lightning fast HMR by vite is interesting.
• Why not use them together ?

Options

// vue.config.js
{
  // ...
  pluginOptions: {
    vite: {
      /**
       * Plugin[]
       * @default []
       */
      plugins: [], // other vite plugins list, will be merge into this plugin\'s underlying vite.config.ts
      /**
       * Vite UserConfig.optimizeDeps options
       * recommended set `include` for speedup page-loaded time, e.g. include: ['vue', 'vue-router', '@scope/xxx']
       * @default {}
       */
      optimizeDeps: {},
      /**
       * type-checker, recommended disabled for large-scale old project.
       * @default false
       */
      disabledTypeChecker: true,
      /**
       * lint code by eslint
       * @default false
       */
      disabledLint: false,
    }
  },
}

• see all

Underlying principle

Compatibility

• NO EXTRA files, code and dependencies injected
  • injected one devDependency vue-cli-plugin-vite
  • injected one line code in package.json#scripts#vite and one file at bin/vite
• auto-resolved as much options as we can from vue.config.js (publicPath, alias, outputDir...)
• auto reuse public/index.html as vite html entry template
• compatible the differences between vue-cli and vite(environment variables, special syntax...)

Differences between vue-cli and vite

Dimension	vue-cli	vite
Plugin	1. based on webpack.  2. have service and generator lifecycles.  3. hooks based on each webpack plugin hooks	1. based on rollup.  2. no generator lifecycle.  3. universal hooks based on rollup plugin hooks and vite self designed
Environment Variables	1. loaded on process.env.  2. prefixed by VUE_APP_.  3. client-side use process.env.VUE_APP_XXX by webpack definePlugin	1. not loaded on process.env.  2. prefixed by VITE_.  3. client-side use import.meta.env.VITE_XXX by vite inner define plugin
Entry Files	1. main.{js,ts}.	1. *.html
Config File	1. vue.config.js	1. vite.config.ts.  2. support use --config to locate
MPA Support	1. native support by options.pages.  2. with history rewrite support	1. native support by rollupOptions.input
Special Syntax	1. require(by webpack)  2. require.context(by webpack)  2. use ~some-module/dist/index.css(by css-loader)  3. module.hot for HMR	1. import.meta.glob/globEager  2. native support by vite, use module/dist/index.css directly  3. import.meta.hot for HMR
Local devServer	1. webpack dev-server  2. express-style middleware and many extension api.	1. connect  2. connect middleware
Type Checker	1. fork-ts-checker-webpack-plugin	1. No built-in, we can use vite-plugin-checker(based on vetur and vue-tsc)
Lint	1. @vue/cli-plugin-eslint	1. No built-in we can use vite-plugin-eslint,
Jest	1. @vue/cli-plugin-jest	1. will have first-class jest support

Milestones

• Done ✅ vs WIP ⬜️ vs ❌ Won't support
• ✅ Plugin
  • ✅ we can do nothing but rewrite corresponding vite-plugin, most code and tools can be reused
• ✅ Environment Variables Compatibility
  • ✅ load to process.env.XXX (all env with or without prefix will be loaded)
  • ✅ recognize VUE_APP_ prefix
  • ✅ define as process.env.${PREFIX}_XXX for client-side
• ✅ Entry Files (we can do nothing)
• ✅ Config File (vue.config.js Options auto-resolved)
  • ✅ vite#base - resolved from process.env.PUBLIC_URL || vue.config.js#publicPath || baseUrl
  • ✅ vite#css - resolved from vue.config.js#css
    • ✅ preprocessorOptions: css.loaderOptions
  • ✅ vite#server- resolved from vue.config.js#devServer
    • ✅ host - resolved from process.env.DEV_HOST || devServer.public
    • ✅ port - resolved from Number(process.env.PORT) || devServer.port
    • ✅ https - resolved from devServer.https
    • ✅ open - resolved from process.platform === 'darwin' || devServer.open
    • ✅ proxy - resolved from devServer.proxy
    • ✅ before
      • use middlewares to improve viteDevServer(connect instance) to express instance
  • ✅ vite#build
    • ✅ outDir - resolved from vue.config.js#outputDir
    • ✅ cssCodeSplit - resolved from css.extract
    • ✅ sourcemap - resolved from process.env.GENERATE_SOURCEMAP === 'true' || productionSourceMap || css.sourceMap
  • ✅ Alias - resolved from configureWebpack or chainWebpack
    • ✅ also resolved from vue.config.js#runtimeCompiler
• ✅ MPA Support
  • ✅ same development experience and build result
• ✅ Build Support (as of 1.0.0-rc.0, no real html entry file generated, just reuse public/index.html of vue-cli)
  • ✅ Support SPA Build
  • ✅ Support MPA Build
• ✅ Special Synatax
  • ❌ require('xxx') or require('xxx').default, most of the case, it can be replaced by dynamicImport ( import('xxx') or import('xxx').then(module => module.default) )
  • ✅ import '~some-module/theme/index.css' syntax for Import CSS supported by vite#2185)
  • ✅ import '~@some-module/theme/index.css' syntax for Import CSS supported by vite#2185)
  • ✅ ~public & ~/public support
  • ✅ require.context compatibility
  • ✅ module.hot compatibilite
• ✅ Type Checker
  • ✅ vite-plugin-checker & vite-plugin-checker-vls
• ✅ Lint
  • ✅ vite-plugin-eslint
• ⬜️ Eject and Codemod
  • ⬜️ eject vite.config.ts
  • ⬜️ eject vite deps
  • ⬜️ remove vue-cli and webpack deps
  • ⬜️ codemod webpack special syntax to vite-specific( import.meta.{hot, env} )

Examples

• simple vue-cli SPA project
• simple vue-cli MPA TypeScript project
• complex chrisvfritz/vue-enterprise-boilerplate project

you can clone/fork this repo, under examples/*

Troubleshooting

• see #9

Benefits

Best development-experience right now

• Instant server start and lightning fast HMR

Migration to vite smoothly

• In the future, migration to vite is only the replacement of special syntax between webpack and vite

Lint the codebase

• lint dependencies, which is incorrectly use main/module/exports field in package.json
• lint codebase, which is more es-module compatible
  • use import('xxx') not require('xxx')
  • use import.meta.xxx not module.xxx

Use vue-cli ecosystem

• first-class eslint/stylelint integration
• first-class unit-test integration (by @vue/cli-plugin-unit-jest)
• first-class e2e integration (by @vue/cli-plugin-cypress)
• first-class xyz support by the official and community plugins

Relevant Vite Plugins

• vite-plugin-vue2@underfin - Vue 2 support for vite.
• @vitejs/plugin-vue - Official Vue 3 plugin.
• @vitejs/plugin-vue-jsx - Official Vue 3 jsx plugin.
• vite-plugin-vue-cli@IndexXuan - Infer vite config from vue.config.js.
• vite-plugin-html-template@IndexXuan - Like html-webpack-plugin for webpack.
• vite-plugin-mpa@IndexXuan - MPA support for vite.
• vite-plugin-checker@fi3ework - Type checker for vite.
• vite-plugin-eslint@gxmari007 - Eslint for vite.
• vite-plugin-env-compatible@IndexXuan - Env compatibility for vite with vue-cli.

---

Author: IndexXuan
Source Code: https://github.com/IndexXuan/vue-cli-plugin-vite
License: MIT license

#vue #vite 

What is GEEK

Buddha Community

Pdf2gerb: Perl Script Converts PDF Files to Gerber format

pdf2gerb

Perl script converts PDF files to Gerber format

Pdf2Gerb generates Gerber 274X photoplotting and Excellon drill files from PDFs of a PCB. Up to three PDFs are used: the top copper layer, the bottom copper layer (for 2-sided PCBs), and an optional silk screen layer. The PDFs can be created directly from any PDF drawing software, or a PDF print driver can be used to capture the Print output if the drawing software does not directly support output to PDF.

The general workflow is as follows:

1. Design the PCB using your favorite CAD or drawing software.
2. Print the top and bottom copper and top silk screen layers to a PDF file.
3. Run Pdf2Gerb on the PDFs to create Gerber and Excellon files.
4. Use a Gerber viewer to double-check the output against the original PCB design.
5. Make adjustments as needed.
6. Submit the files to a PCB manufacturer.

Please note that Pdf2Gerb does NOT perform DRC (Design Rule Checks), as these will vary according to individual PCB manufacturer conventions and capabilities. Also note that Pdf2Gerb is not perfect, so the output files must always be checked before submitting them. As of version 1.6, Pdf2Gerb supports most PCB elements, such as round and square pads, round holes, traces, SMD pads, ground planes, no-fill areas, and panelization. However, because it interprets the graphical output of a Print function, there are limitations in what it can recognize (or there may be bugs).

See docs/Pdf2Gerb.pdf for install/setup, config, usage, and other info.

---

pdf2gerb_cfg.pm

#Pdf2Gerb config settings:
#Put this file in same folder/directory as pdf2gerb.pl itself (global settings),
#or copy to another folder/directory with PDFs if you want PCB-specific settings.
#There is only one user of this file, so we don't need a custom package or namespace.
#NOTE: all constants defined in here will be added to main namespace.
#package pdf2gerb_cfg;

use strict; #trap undef vars (easier debug)
use warnings; #other useful info (easier debug)


##############################################################################################
#configurable settings:
#change values here instead of in main pfg2gerb.pl file

use constant WANT_COLORS => ($^O !~ m/Win/); #ANSI colors no worky on Windows? this must be set < first DebugPrint() call

#just a little warning; set realistic expectations:
#DebugPrint("${\(CYAN)}Pdf2Gerb.pl ${\(VERSION)}, $^O O/S\n${\(YELLOW)}${\(BOLD)}${\(ITALIC)}This is EXPERIMENTAL software.  \nGerber files MAY CONTAIN ERRORS.  Please CHECK them before fabrication!${\(RESET)}", 0); #if WANT_DEBUG

use constant METRIC => FALSE; #set to TRUE for metric units (only affect final numbers in output files, not internal arithmetic)
use constant APERTURE_LIMIT => 0; #34; #max #apertures to use; generate warnings if too many apertures are used (0 to not check)
use constant DRILL_FMT => '2.4'; #'2.3'; #'2.4' is the default for PCB fab; change to '2.3' for CNC

use constant WANT_DEBUG => 0; #10; #level of debug wanted; higher == more, lower == less, 0 == none
use constant GERBER_DEBUG => 0; #level of debug to include in Gerber file; DON'T USE FOR FABRICATION
use constant WANT_STREAMS => FALSE; #TRUE; #save decompressed streams to files (for debug)
use constant WANT_ALLINPUT => FALSE; #TRUE; #save entire input stream (for debug ONLY)

#DebugPrint(sprintf("${\(CYAN)}DEBUG: stdout %d, gerber %d, want streams? %d, all input? %d, O/S: $^O, Perl: $]${\(RESET)}\n", WANT_DEBUG, GERBER_DEBUG, WANT_STREAMS, WANT_ALLINPUT), 1);
#DebugPrint(sprintf("max int = %d, min int = %d\n", MAXINT, MININT), 1); 

#define standard trace and pad sizes to reduce scaling or PDF rendering errors:
#This avoids weird aperture settings and replaces them with more standardized values.
#(I'm not sure how photoplotters handle strange sizes).
#Fewer choices here gives more accurate mapping in the final Gerber files.
#units are in inches
use constant TOOL_SIZES => #add more as desired
(
#round or square pads (> 0) and drills (< 0):
    .010, -.001,  #tiny pads for SMD; dummy drill size (too small for practical use, but needed so StandardTool will use this entry)
    .031, -.014,  #used for vias
    .041, -.020,  #smallest non-filled plated hole
    .051, -.025,
    .056, -.029,  #useful for IC pins
    .070, -.033,
    .075, -.040,  #heavier leads
#    .090, -.043,  #NOTE: 600 dpi is not high enough resolution to reliably distinguish between .043" and .046", so choose 1 of the 2 here
    .100, -.046,
    .115, -.052,
    .130, -.061,
    .140, -.067,
    .150, -.079,
    .175, -.088,
    .190, -.093,
    .200, -.100,
    .220, -.110,
    .160, -.125,  #useful for mounting holes
#some additional pad sizes without holes (repeat a previous hole size if you just want the pad size):
    .090, -.040,  #want a .090 pad option, but use dummy hole size
    .065, -.040, #.065 x .065 rect pad
    .035, -.040, #.035 x .065 rect pad
#traces:
    .001,  #too thin for real traces; use only for board outlines
    .006,  #minimum real trace width; mainly used for text
    .008,  #mainly used for mid-sized text, not traces
    .010,  #minimum recommended trace width for low-current signals
    .012,
    .015,  #moderate low-voltage current
    .020,  #heavier trace for power, ground (even if a lighter one is adequate)
    .025,
    .030,  #heavy-current traces; be careful with these ones!
    .040,
    .050,
    .060,
    .080,
    .100,
    .120,
);
#Areas larger than the values below will be filled with parallel lines:
#This cuts down on the number of aperture sizes used.
#Set to 0 to always use an aperture or drill, regardless of size.
use constant { MAX_APERTURE => max((TOOL_SIZES)) + .004, MAX_DRILL => -min((TOOL_SIZES)) + .004 }; #max aperture and drill sizes (plus a little tolerance)
#DebugPrint(sprintf("using %d standard tool sizes: %s, max aper %.3f, max drill %.3f\n", scalar((TOOL_SIZES)), join(", ", (TOOL_SIZES)), MAX_APERTURE, MAX_DRILL), 1);

#NOTE: Compare the PDF to the original CAD file to check the accuracy of the PDF rendering and parsing!
#for example, the CAD software I used generated the following circles for holes:
#CAD hole size:   parsed PDF diameter:      error:
#  .014                .016                +.002
#  .020                .02267              +.00267
#  .025                .026                +.001
#  .029                .03167              +.00267
#  .033                .036                +.003
#  .040                .04267              +.00267
#This was usually ~ .002" - .003" too big compared to the hole as displayed in the CAD software.
#To compensate for PDF rendering errors (either during CAD Print function or PDF parsing logic), adjust the values below as needed.
#units are pixels; for example, a value of 2.4 at 600 dpi = .0004 inch, 2 at 600 dpi = .0033"
use constant
{
    HOLE_ADJUST => -0.004 * 600, #-2.6, #holes seemed to be slightly oversized (by .002" - .004"), so shrink them a little
    RNDPAD_ADJUST => -0.003 * 600, #-2, #-2.4, #round pads seemed to be slightly oversized, so shrink them a little
    SQRPAD_ADJUST => +0.001 * 600, #+.5, #square pads are sometimes too small by .00067, so bump them up a little
    RECTPAD_ADJUST => 0, #(pixels) rectangular pads seem to be okay? (not tested much)
    TRACE_ADJUST => 0, #(pixels) traces seemed to be okay?
    REDUCE_TOLERANCE => .001, #(inches) allow this much variation when reducing circles and rects
};

#Also, my CAD's Print function or the PDF print driver I used was a little off for circles, so define some additional adjustment values here:
#Values are added to X/Y coordinates; units are pixels; for example, a value of 1 at 600 dpi would be ~= .002 inch
use constant
{
    CIRCLE_ADJUST_MINX => 0,
    CIRCLE_ADJUST_MINY => -0.001 * 600, #-1, #circles were a little too high, so nudge them a little lower
    CIRCLE_ADJUST_MAXX => +0.001 * 600, #+1, #circles were a little too far to the left, so nudge them a little to the right
    CIRCLE_ADJUST_MAXY => 0,
    SUBST_CIRCLE_CLIPRECT => FALSE, #generate circle and substitute for clip rects (to compensate for the way some CAD software draws circles)
    WANT_CLIPRECT => TRUE, #FALSE, #AI doesn't need clip rect at all? should be on normally?
    RECT_COMPLETION => FALSE, #TRUE, #fill in 4th side of rect when 3 sides found
};

#allow .012 clearance around pads for solder mask:
#This value effectively adjusts pad sizes in the TOOL_SIZES list above (only for solder mask layers).
use constant SOLDER_MARGIN => +.012; #units are inches

#line join/cap styles:
use constant
{
    CAP_NONE => 0, #butt (none); line is exact length
    CAP_ROUND => 1, #round cap/join; line overhangs by a semi-circle at either end
    CAP_SQUARE => 2, #square cap/join; line overhangs by a half square on either end
    CAP_OVERRIDE => FALSE, #cap style overrides drawing logic
};
    
#number of elements in each shape type:
use constant
{
    RECT_SHAPELEN => 6, #x0, y0, x1, y1, count, "rect" (start, end corners)
    LINE_SHAPELEN => 6, #x0, y0, x1, y1, count, "line" (line seg)
    CURVE_SHAPELEN => 10, #xstart, ystart, x0, y0, x1, y1, xend, yend, count, "curve" (bezier 2 points)
    CIRCLE_SHAPELEN => 5, #x, y, 5, count, "circle" (center + radius)
};
#const my %SHAPELEN =
#Readonly my %SHAPELEN =>
our %SHAPELEN =
(
    rect => RECT_SHAPELEN,
    line => LINE_SHAPELEN,
    curve => CURVE_SHAPELEN,
    circle => CIRCLE_SHAPELEN,
);

#panelization:
#This will repeat the entire body the number of times indicated along the X or Y axes (files grow accordingly).
#Display elements that overhang PCB boundary can be squashed or left as-is (typically text or other silk screen markings).
#Set "overhangs" TRUE to allow overhangs, FALSE to truncate them.
#xpad and ypad allow margins to be added around outer edge of panelized PCB.
use constant PANELIZE => {'x' => 1, 'y' => 1, 'xpad' => 0, 'ypad' => 0, 'overhangs' => TRUE}; #number of times to repeat in X and Y directions

# Set this to 1 if you need TurboCAD support.
#$turboCAD = FALSE; #is this still needed as an option?

#CIRCAD pad generation uses an appropriate aperture, then moves it (stroke) "a little" - we use this to find pads and distinguish them from PCB holes. 
use constant PAD_STROKE => 0.3; #0.0005 * 600; #units are pixels
#convert very short traces to pads or holes:
use constant TRACE_MINLEN => .001; #units are inches
#use constant ALWAYS_XY => TRUE; #FALSE; #force XY even if X or Y doesn't change; NOTE: needs to be TRUE for all pads to show in FlatCAM and ViewPlot
use constant REMOVE_POLARITY => FALSE; #TRUE; #set to remove subtractive (negative) polarity; NOTE: must be FALSE for ground planes

#PDF uses "points", each point = 1/72 inch
#combined with a PDF scale factor of .12, this gives 600 dpi resolution (1/72 * .12 = 600 dpi)
use constant INCHES_PER_POINT => 1/72; #0.0138888889; #multiply point-size by this to get inches

# The precision used when computing a bezier curve. Higher numbers are more precise but slower (and generate larger files).
#$bezierPrecision = 100;
use constant BEZIER_PRECISION => 36; #100; #use const; reduced for faster rendering (mainly used for silk screen and thermal pads)

# Ground planes and silk screen or larger copper rectangles or circles are filled line-by-line using this resolution.
use constant FILL_WIDTH => .01; #fill at most 0.01 inch at a time

# The max number of characters to read into memory
use constant MAX_BYTES => 10 * M; #bumped up to 10 MB, use const

use constant DUP_DRILL1 => TRUE; #FALSE; #kludge: ViewPlot doesn't load drill files that are too small so duplicate first tool

my $runtime = time(); #Time::HiRes::gettimeofday(); #measure my execution time

print STDERR "Loaded config settings from '${\(__FILE__)}'.\n";
1; #last value must be truthful to indicate successful load


#############################################################################################
#junk/experiment:

#use Package::Constants;
#use Exporter qw(import); #https://perldoc.perl.org/Exporter.html

#my $caller = "pdf2gerb::";

#sub cfg
#{
#    my $proto = shift;
#    my $class = ref($proto) || $proto;
#    my $settings =
#    {
#        $WANT_DEBUG => 990, #10; #level of debug wanted; higher == more, lower == less, 0 == none
#    };
#    bless($settings, $class);
#    return $settings;
#}

#use constant HELLO => "hi there2"; #"main::HELLO" => "hi there";
#use constant GOODBYE => 14; #"main::GOODBYE" => 12;

#print STDERR "read cfg file\n";

#our @EXPORT_OK = Package::Constants->list(__PACKAGE__); #https://www.perlmonks.org/?node_id=1072691; NOTE: "_OK" skips short/common names

#print STDERR scalar(@EXPORT_OK) . " consts exported:\n";
#foreach(@EXPORT_OK) { print STDERR "$_\n"; }
#my $val = main::thing("xyz");
#print STDERR "caller gave me $val\n";
#foreach my $arg (@ARGV) { print STDERR "arg $arg\n"; }

---

Download Details:

Author: swannman
Source Code: https://github.com/swannman/pdf2gerb

License: GPL-3.0 license

#perl 

Vue Cli Plugin Vite: Use Vite today, with Vue-cli.

Use Vite Today

out-of-the-box for vue-cli projects without any codebase modifications.

demo/boilerplate

Usage

# 1. first step
vue add vite

# 2. second step
# NOTE you cannot directly use `vite` or `npx vite` since it is origin vite not this plugin.
yarn vite // or npm run vite

# 3. add optimizeDeps#include (optional and will speedup devServer start time a lot)
# added in vue.config.js#pluginOptions.vite.optimizeDeps.include
# e.g.: ['vue', 'vue-router', 'vuex']
# all scanned deps(logged in terminal) can be added for speedup.

Motivation

• We have lots of exists vue-cli(3.x / 4.x) projects.
• In Production: vue-cli based on webpack is still the best practice for bundling webapp(with code spliting, legecy-build for old browsers).
• In Development: instant server start and lightning fast HMR by vite is interesting.
• Why not use them together ?

Options

// vue.config.js
{
  // ...
  pluginOptions: {
    vite: {
      /**
       * Plugin[]
       * @default []
       */
      plugins: [], // other vite plugins list, will be merge into this plugin\'s underlying vite.config.ts
      /**
       * Vite UserConfig.optimizeDeps options
       * recommended set `include` for speedup page-loaded time, e.g. include: ['vue', 'vue-router', '@scope/xxx']
       * @default {}
       */
      optimizeDeps: {},
      /**
       * type-checker, recommended disabled for large-scale old project.
       * @default false
       */
      disabledTypeChecker: true,
      /**
       * lint code by eslint
       * @default false
       */
      disabledLint: false,
    }
  },
}

• see all

Underlying principle

Compatibility

• NO EXTRA files, code and dependencies injected
  • injected one devDependency vue-cli-plugin-vite
  • injected one line code in package.json#scripts#vite and one file at bin/vite
• auto-resolved as much options as we can from vue.config.js (publicPath, alias, outputDir...)
• auto reuse public/index.html as vite html entry template
• compatible the differences between vue-cli and vite(environment variables, special syntax...)

Differences between vue-cli and vite

Dimension	vue-cli	vite
Plugin	1. based on webpack.  2. have service and generator lifecycles.  3. hooks based on each webpack plugin hooks	1. based on rollup.  2. no generator lifecycle.  3. universal hooks based on rollup plugin hooks and vite self designed
Environment Variables	1. loaded on process.env.  2. prefixed by VUE_APP_.  3. client-side use process.env.VUE_APP_XXX by webpack definePlugin	1. not loaded on process.env.  2. prefixed by VITE_.  3. client-side use import.meta.env.VITE_XXX by vite inner define plugin
Entry Files	1. main.{js,ts}.	1. *.html
Config File	1. vue.config.js	1. vite.config.ts.  2. support use --config to locate
MPA Support	1. native support by options.pages.  2. with history rewrite support	1. native support by rollupOptions.input
Special Syntax	1. require(by webpack)  2. require.context(by webpack)  2. use ~some-module/dist/index.css(by css-loader)  3. module.hot for HMR	1. import.meta.glob/globEager  2. native support by vite, use module/dist/index.css directly  3. import.meta.hot for HMR
Local devServer	1. webpack dev-server  2. express-style middleware and many extension api.	1. connect  2. connect middleware
Type Checker	1. fork-ts-checker-webpack-plugin	1. No built-in, we can use vite-plugin-checker(based on vetur and vue-tsc)
Lint	1. @vue/cli-plugin-eslint	1. No built-in we can use vite-plugin-eslint,
Jest	1. @vue/cli-plugin-jest	1. will have first-class jest support

Milestones

• Done ✅ vs WIP ⬜️ vs ❌ Won't support
• ✅ Plugin
  • ✅ we can do nothing but rewrite corresponding vite-plugin, most code and tools can be reused
• ✅ Environment Variables Compatibility
  • ✅ load to process.env.XXX (all env with or without prefix will be loaded)
  • ✅ recognize VUE_APP_ prefix
  • ✅ define as process.env.${PREFIX}_XXX for client-side
• ✅ Entry Files (we can do nothing)
• ✅ Config File (vue.config.js Options auto-resolved)
  • ✅ vite#base - resolved from process.env.PUBLIC_URL || vue.config.js#publicPath || baseUrl
  • ✅ vite#css - resolved from vue.config.js#css
    • ✅ preprocessorOptions: css.loaderOptions
  • ✅ vite#server- resolved from vue.config.js#devServer
    • ✅ host - resolved from process.env.DEV_HOST || devServer.public
    • ✅ port - resolved from Number(process.env.PORT) || devServer.port
    • ✅ https - resolved from devServer.https
    • ✅ open - resolved from process.platform === 'darwin' || devServer.open
    • ✅ proxy - resolved from devServer.proxy
    • ✅ before
      • use middlewares to improve viteDevServer(connect instance) to express instance
  • ✅ vite#build
    • ✅ outDir - resolved from vue.config.js#outputDir
    • ✅ cssCodeSplit - resolved from css.extract
    • ✅ sourcemap - resolved from process.env.GENERATE_SOURCEMAP === 'true' || productionSourceMap || css.sourceMap
  • ✅ Alias - resolved from configureWebpack or chainWebpack
    • ✅ also resolved from vue.config.js#runtimeCompiler
• ✅ MPA Support
  • ✅ same development experience and build result
• ✅ Build Support (as of 1.0.0-rc.0, no real html entry file generated, just reuse public/index.html of vue-cli)
  • ✅ Support SPA Build
  • ✅ Support MPA Build
• ✅ Special Synatax
  • ❌ require('xxx') or require('xxx').default, most of the case, it can be replaced by dynamicImport ( import('xxx') or import('xxx').then(module => module.default) )
  • ✅ import '~some-module/theme/index.css' syntax for Import CSS supported by vite#2185)
  • ✅ import '~@some-module/theme/index.css' syntax for Import CSS supported by vite#2185)
  • ✅ ~public & ~/public support
  • ✅ require.context compatibility
  • ✅ module.hot compatibilite
• ✅ Type Checker
  • ✅ vite-plugin-checker & vite-plugin-checker-vls
• ✅ Lint
  • ✅ vite-plugin-eslint
• ⬜️ Eject and Codemod
  • ⬜️ eject vite.config.ts
  • ⬜️ eject vite deps
  • ⬜️ remove vue-cli and webpack deps
  • ⬜️ codemod webpack special syntax to vite-specific( import.meta.{hot, env} )

Examples

• simple vue-cli SPA project
• simple vue-cli MPA TypeScript project
• complex chrisvfritz/vue-enterprise-boilerplate project

you can clone/fork this repo, under examples/*

Troubleshooting

• see #9

Benefits

Best development-experience right now

• Instant server start and lightning fast HMR

Migration to vite smoothly

• In the future, migration to vite is only the replacement of special syntax between webpack and vite

Lint the codebase

• lint dependencies, which is incorrectly use main/module/exports field in package.json
• lint codebase, which is more es-module compatible
  • use import('xxx') not require('xxx')
  • use import.meta.xxx not module.xxx

Use vue-cli ecosystem

• first-class eslint/stylelint integration
• first-class unit-test integration (by @vue/cli-plugin-unit-jest)
• first-class e2e integration (by @vue/cli-plugin-cypress)
• first-class xyz support by the official and community plugins

Relevant Vite Plugins

• vite-plugin-vue2@underfin - Vue 2 support for vite.
• @vitejs/plugin-vue - Official Vue 3 plugin.
• @vitejs/plugin-vue-jsx - Official Vue 3 jsx plugin.
• vite-plugin-vue-cli@IndexXuan - Infer vite config from vue.config.js.
• vite-plugin-html-template@IndexXuan - Like html-webpack-plugin for webpack.
• vite-plugin-mpa@IndexXuan - MPA support for vite.
• vite-plugin-checker@fi3ework - Type checker for vite.
• vite-plugin-eslint@gxmari007 - Eslint for vite.
• vite-plugin-env-compatible@IndexXuan - Env compatibility for vite with vue-cli.

---

Author: IndexXuan
Source Code: https://github.com/IndexXuan/vue-cli-plugin-vite
License: MIT license

#vue #vite 

8 Popular Websites That Use The Vue.JS Framework

In this article, we are going to list out the most popular websites using Vue JS as their frontend framework.

Vue JS is one of those elite progressive JavaScript frameworks that has huge demand in the web development industry. Many popular websites are developed using Vue in their frontend development because of its imperative features.

This framework was created by Evan You and still it is maintained by his private team members. Vue is of course an open-source framework which is based on MVVM concept (Model-view view-Model) and used extensively in building sublime user-interfaces and also considered a prime choice for developing single-page heavy applications.

Released in February 2014, Vue JS has gained 64,828 stars on Github, making it very popular in recent times.

Evan used Angular JS on many operations while working for Google and integrated many features in Vue to cover the flaws of Angular.

“I figured, what if I could just extract the part that I really liked about Angular and build something really lightweight." - Evan You

#vuejs #vue #vue-with-laravel #vue-top-story #vue-3 #build-vue-frontend #vue-in-laravel #vue.js

Vue CLI plugin development.

Problem statement

To create a CLI command, which can create a boilerplate for me(like how vue create does). But for my use case, I want to add some predefined packages, scripts, husky. To enforce some rules (best practices), So everyone in my organization will be on the same page.
And also, to allow the developer to select some inhouse npm packages so that based on the selection, those packages will be installed, and even some code will be injected into the files dynamically.

Why I am writing this article

To achieve the above problem statement, I researched a lot and came to know about vue-CLI-plugin-development, which has excellent documentation but a lack of good examples. So I thought of writing one article which can help you to solve some of the things when you are building a CLI plugin. Let us start.

#vuejs #vue #vue-cli #vue-plugin

Vue File Upload Using vue-dropzone Tutorial

In this tutorial, I will show you how to upload a file in Vue using vue-dropzone library. For this example, I am using Vue.js 3.0. First, we will install the Vue.js using Vue CLI, and then we install the vue-dropzone library. Then configure it, and we are ready to accept the file. DropzoneJS is an open source library that provides drag and drops file uploads with image previews. DropzoneJS is lightweight doesn’t depend on any other library (like jQuery) and is  highly customizable. The  vue-dropzone is a vue component implemented on top of Dropzone.js. Let us start Vue File Upload Using vue-dropzone Tutorial.

Dropzone.js is an open-source library providing drag-and-drop file uploads with image previews. DropzoneJS is lightweight, doesn’t depend on any other library (like jQuery), and is highly customizable.

The vue-dropzone is a vue component implemented on top of Dropzone.js.

First, install the Vue using Vue CLI.

Step 1: Install Vue.js using Vue CLI.

Go to your terminal and hit the following command.

npm install -g @vue/cli
         or
yarn global add @vue/cli

If you face any error, try running the command as an administrator.

Now, we need to generate the necessary scaffold. So type the following command.

vue create vuedropzone

It will install the scaffold.

Open the project in your favorite editor. Mine is Visual Studio Code.

cd vuedropzone
code .

Step 2: Install vue-dropzone.

I am using the Yarn package manager. So let’s install using Yarn. You can use NPM, also. It does not matter.

yarn add vue2-dropzone

or

npm install vue2-dropzone

Okay, now we need to add one css file with the above package. Now, vue cli uses css loader, so we can directly import in the src >>  main.js entry file.

import Vue from 'vue'
import App from './App.vue'

Vue.config.productionTip = false

new Vue({
  render: h => h(App)
}).$mount('#app')

import 'vue2-dropzone/dist/vue2Dropzone.css'

If importing css is not working for you, then you need to install that CSS file manually.

Copy this vue2Dropzone.css file’s content.

Create one file inside the src  >>  assets folder, create one css file called vuedropzone.css and paste the content there.

Import this css file inside src  >>  App.vue file.

<style lang="css">
  @import './assets/vuedropzone.css';
</style>

Now, it should include in our application.

Step 3: Upload an Image.

Our primary boilerplate has one ready-made component called HelloWorld.vue inside src  >>  components folder. Now, create one more file called FileUpload.vue.

Add the following code to FileUpload.vue file.

// FileUpload.vue

<template>
  <div id="app">
    <vue-dropzone id="upload" :options="config"></vue-dropzone>
  </div>
</template>

<script>
import vueDropzone from "vue2-dropzone";

export default {
  data: () => ({
    config: {
      url: "https://appdividend.com"
    }
  }),
  components: {
    vueDropzone
  }
};
</script>

Here, our API endpoint is https://appdividend.com. It is the point where we will hit the POST route and store our image, but it is my blog’s homepage, so it will not work anyway. But let me import this file into App.vue component and see what happens.

// App.vue

<template>
  <div id="app">
    <FileUpload />
  </div>
</template>

<script>
import FileUpload from './components/FileUpload.vue'

export default {
  name: 'app',
  components: {
    FileUpload
  }
}
</script>

<style lang="css">
  @import './assets/vuedropzone.css';
</style>

Now, start the development server using the following command. It will open up URL: http://localhost:8080.

npm run serve

Now, after uploading the image, we can see that the image upload is failed due to the wrong POST request endpoint.

Step 4: Create Laravel API for the endpoint.

Install the Laravel.

After that, we configure the database in the .env file and use MySQL database.

We need to create one model and migration file to store the image. So let us install the following command inside the Laravel project.

php artisan make:model Image -m

It will create both the Image model and create_images_table.php migrations file.

Now, open the migrations file and add the schema to it.

// create_images_table.php

public function up()
    {
        Schema::create('images', function (Blueprint $table) {
            $table->increments('id');
            $table->string('image_name');
            $table->timestamps();
        });
    }

Now, migrate the database table using the following command.

php artisan migrate

It creates the table in the database.

Now, we need to add a laravel-cors package to prevent cross-site-allow-origin errors. Go to the Laravel root and enter the following command to install it.

composer require barryvdh/laravel-cors

Configure it in the config  >>  app.php file.

Barryvdh\Cors\ServiceProvider::class,

Add the middleware inside app >>  Http  >>  Kernel.php file.

// Kernel.php

protected $middleware = [
        \Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode::class,
        \Illuminate\Foundation\Http\Middleware\ValidatePostSize::class,
        \App\Http\Middleware\TrimStrings::class,
        \Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull::class,
        \App\Http\Middleware\TrustProxies::class,
        \Barryvdh\Cors\HandleCors::class,
];

Step 5: Define the API route and method to store the image.

First, create an ImageController.php file using the following command.

php artisan make:controller ImageController

Define the store method. Also, create one images folder inside the public directory because we will store an image inside it.

Right now, I have written the store function that handles one image at a time. So do not upload multiple photos at a time; otherwise, it will break.

// ImageController.php

<?php

namespace App\Http\Controllers;

use Illuminate\Http\Request;
use App\Image;

class ImageController extends Controller
{
    public function store(Request $request)
    {
       if($request->file('file'))
       {
          $image = $request->file('file');
          $name = time().$image->getClientOriginalName();
          $image->move(public_path().'/images/', $name); 
        }

       $image= new Image();
       $image->image_name = $name;
       $image->save();

       return response()->json(['success' => 'You have successfully uploaded an image'], 200);
     }
}

Go to the routes   >>  api.php file and add the following route.

// api.php

Route::post('image', 'ImageController@store');

Step 6: Edit FileUpload.vue component.

We need to add the correct Post request API endpoint in FileUpload.vue component.

// FileUpload.vue

<template>
  <div id="app">
    <vue-dropzone id="drop1" :options="config" @vdropzone-complete="afterComplete"></vue-dropzone>
  </div>
</template>

<script>
import vueDropzone from "vue2-dropzone";

export default {
  data: () => ({
    config: {
      url: "http://localhost:8000/api/image",
      
    }
  }),
  components: {
    vueDropzone
  },
  methods: {
    afterComplete(file) {
      console.log(file);
    }
  }
};
</script>

Now, save the file and try to upload an image. If everything is okay, then you will be able to save the image on the Laravel web server as well as save the name in the database as well.

You can also verify on the server side by checking the database entry and the images folder in which we have saved the image.

Step 7: More vue-dropzone configuration.

The only required options are url, but there are many more you can use.

For example, let’s say you want:

• A maximum of 4 files
• 2 MB max file size
• Sent in chunks of 500 bytes
• Set a custom thumbnail size of 150px
• Make the uploaded items cancelable and removable (by default, they’re not)

export default {
  data: () => ({
    dropOptions: {
      url: "https://httpbin.org/post",
      maxFilesize: 5, // MB
      maxFiles: 5,
      chunking: true,
      chunkSize: 400, // Bytes
      thumbnailWidth: 100, // px
      thumbnailHeight: 100,
      addRemoveLinks: true
    }
  })
  // ...
}

Happy Coding !!!

Originally published at https://appdividend.com 

#vue #vue-dropzone #vue.js #dropzone.js #dropzonejs #vue cli