JSPM

  • Created
  • Published
  • Downloads 315742
  • Score
    100M100P100Q180245F
  • License MIT

Enhance Vite builtin dynamic import

Package Exports

  • vite-plugin-dynamic-import
  • vite-plugin-dynamic-import/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (vite-plugin-dynamic-import) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

vite-plugin-dynamic-import

Enhance Vite builtin dynamic import

NPM version NPM Downloads awesome-vite

English | 简体中文

✅ alias
✅ bare module(node_modules)
✅ compatible @rollup/plugin-dynamic-import-vars limitations

Install

npm i vite-plugin-dynamic-import -D

Usage

import dynamicImport from 'vite-plugin-dynamic-import'

export default {
  plugins: [
    dynamicImport(/* options */)
  ]
}

cases 👉 vite-plugin-dynamic-import/test

API

dynamicImport([options])

export interface Options {
  filter?: (id: string) => false | void
  /**
   * This option will change `./*` to `./** /*`
   * @default true
   */
  depth?: boolean
  /**
   * If you want to exclude some files  
   * e.g `type.d.ts`, `interface.ts`
   */
  onFiles?: (files: string[], id: string) => typeof files | void
  /**
   * It will add `@vite-ignore`  
   * `import(/*@vite-ignore* / 'import-path')`
   */
  viteIgnore?: (rawImportee: string, id: string) => true | void
}

How and why?

We assume that the project structure is as follows

├─┬ src
│ ├─┬ views
│ │ ├─┬ foo
│ │ │ └── index.js
│ │ └── bar.js
│ └── router.js
└── vite.config.js
// vite.config.js
export default {
  resolve: {
    alias: {
      // "@" -> "/User/project-root/src/views"
      '@': path.join(__dirname, 'src/views'),
    },
  },
}

Dynamic import is not well supported in Vite, such as

  • Alias are not supported
// router.jsimport(`@/views/${variable}.js`)
  • Must be relative
// router.jsimport(`/User/project-root/src/views/${variable}.js`)
  • Must have extension
// router.jsimport(`./views/${variable}`)

We try to fix these problems

For the alias in import(), we can calculate the relative path according to importer

// router.jsimport(`./views/${variable}.js`)

If the import path has no suffix, we use glob to find the file according to UserConfig.resolve.extensions and supplement the suffix of the import path.
So we need to list all the possibilities

  1. transpire dynamic import variable, yout can see @rollup/plugin-dynamic-import-vars

./views/${variable} -> ./views/*

  1. generate runtime code
- // import(`./views/${variable}`)
+ __variableDynamicImportRuntime(`./views/${variable}`)

+ function __variableDynamicImportRuntime(path) {
+   switch (path) {
+     case 'foo':
+     case 'foo/index':
+     case 'foo/index.js':
+       return import('./views/foo/index.js');
+ 
+     case 'bar':
+     case 'bar.js':
+       return import('./views/bar.js');
+ }