Coder Social home page Coder Social logo

vite-plugin-cesium's Introduction

⚡ vite-plugin-cesium

npm npm

Easily set up a Cesium project in Vite.

update: if you just wanna a scaffolding by using this plugin, try a simply command yarn create cesium, click create-cesium for more info.

Chinese tutorial: 中文教程

Install

npm i cesium vite-plugin-cesium vite -D
# yarn add cesium vite-plugin-cesium vite -D

Usage

add this plugin to vite.config.js

import { defineConfig } from 'vite';
import cesium from 'vite-plugin-cesium';
export default defineConfig({
  plugins: [cesium()]
});

add dev command to package.json

"scripts": {
  "dev": "vite",
  "build": "vite build"
}

run:

yarn dev

Options

rebuildCesium

  • Type : boolean
  • Default : false

Default copy min cesium file to dist. if true will rebuild cesium from source.

import { defineConfig } from 'vite';
import cesium from 'vite-plugin-cesium';
export default defineConfig({
  plugins: [
    cesium({
      rebuildCesium: true
    })
  ]
});

Demo

src/index.js

import { Viewer } from 'cesium';
import './css/main.css';

const viewer = new Viewer('cesiumContainer');

or if you like global Cesium object you can write as

import * as Cesium from 'cesium';
const viewer = new Cesium.Viewer('cesiumContainer');

index.html

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>cesium-vite</title>
    <script type="module" src="/src/index.js"></script>
  </head>

  <body>
    <div id="cesiumContainer"></div>
  </body>
</html>

src/css/main.css

html,
body,
#cesiumContainer {
  width: 100%;
  height: 100%;
  margin: 0;
  padding: 0;
  overflow: hidden;
}

Add dev and build commands to package.json

"scripts": {
    "dev": "vite",
    "build": "vite build"
},

Run yarn dev

For full demo project please check ./demo folder.

License

MIT

vite-plugin-cesium's People

Contributors

amitgk1 avatar an501920078 avatar fairyscript avatar fufuhao avatar gu-miao avatar janhartmann avatar loosheng avatar nshen avatar subdavis avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

vite-plugin-cesium's Issues

Embedded deployment not woring with an empty string as base

With an empty string ("") as base-option Ceisum-assets will get fetched from the root of the webserver no matter where the project was deployed. Therefore, the app will not work in a non-root directory.

With "./" as base everything works as excepted. So there is a workaround. But according to the Vite docs, "" and "./" should both be suitable for embedded deployment.

The plugin does not work in dev mode

The plugin works well in prod mode: compile the project with 'npm run build', and the output dist directory works with nginx.

But when in dev mode with 'npm run dev', the index page does not appear in a brower, and there is an error in browse console:
Uncaught TypeError: Cannot read properties of undefined (reading 'Cartesian3')

I modify the source code of the plugin in node_modules/vite-plugin-cesium/dist/index.js line:96

-              if (isBuild && !rebuildCesium) {
+             if (!rebuildCesium) {

then it works as expeted.

增加配置项outDir和base

现在outDir和base是写死的,在做一个站点多文件夹下面的时候不方便修改。

function vitePluginCesium(options = {
    rebuildCesium: false,
    devMinifyCesium: false,
    outDir: 'dist',
    base: '/'
}) {
    const { rebuildCesium, devMinifyCesium, outDir } = options;
    const cesiumBuildRootPath = 'node_modules/cesium/Build';
    const cesiumBuildPath = 'node_modules/cesium/Build/Cesium/';
    let CESIUM_BASE_URL = '/cesium/';
    let base = options.base
    ....
}

rebuildCesium: true

cesium({
      rebuildCesium: true,
    })

加了rebuildCesium 后打包报错
Cant build with option rebuildCesium

transforming (5977) src\components\Menu\src\components\BasicMenuItem.vue[commonjs] Expecting Unicode escape sequence \uXXXX (65:98) in E:/repo/vue-vben-admin/node_modules/.pnpm/[email protected]/node_modules/cesium/Source/Core/buildModuleUrl.js
file: E:/repo/vue-vben-admin/node_modules/.pnpm/[email protected]/node_modules/cesium/Source/Core/buildModuleUrl.js:65:98
63:   if (!defined(baseUrlString)) {
64:     throw new DeveloperError(
65:       "Unable to determine Cesium base URL automatically, try defining a global variable called "\\cesium\\"."
                                                                                                      ^
66:     );
67:   }
error during build:
SyntaxError: Expecting Unicode escape sequence \uXXXX (65:98) in E:/repo/vue-vben-admin/node_modules/.pnpm/[email protected]/node_modules/cesium/Source/Core/buildModuleUrl.js
    at Parser.pp$4.raise (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:19596:13)
    at Parser.pp.invalidStringToken (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:21481:10)
    at Parser.pp.readWord1 (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:21647:16)
    at Parser.pp.readWord (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:21666:19)
    at Parser.pp.readToken (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:20943:19)
    at Parser.pp.nextToken (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:20936:15)
    at Parser.pp.next (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:20897:8)
    at Parser.pp$5.parseLiteral (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:19034:8)
    at Parser.pp$5.parseExprAtom (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:18920:17)
    at Parser.pp$5.parseExprSubscripts (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:18763:19)
    at Parser.pp$5.parseMaybeUnary (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:18729:17)
    at Parser.pp$5.parseExprOps (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:18656:19)
    at Parser.pp$5.parseMaybeConditional (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:18639:19)
    at Parser.pp$5.parseMaybeAssign (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:18606:19)
    at Parser.pp$5.parseExprList (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:19475:18)
    at Parser.pp$5.parseNew (E:\repo\vue-vben-admin\node_modules\.pnpm\[email protected]\node_modules\rollup\dist\shared\rollup.js:19144:57)
 ELIFECYCLE  Command failed with exit code 1.

Failed to load resource: the server responded with a status of 404 (Not Found)

Failed to load resource: the server responded with a status of 404 (Not Found)

package.json

 "devDependencies": {
    "@vitejs/plugin-vue": "^2.3.0",
    "autoprefixer": "^10.4.4",
    "cesium": "^1.92.0",
    "postcss": "^8.4.12",
    "tailwindcss": "^3.0.23",
    "typescript": "^4.5.4",
    "vite": "^2.9.0",
    "vite-plugin-cesium": "^1.2.15",
    "vue-tsc": "^0.29.8"
  }

vite.config.ts


import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
import cesium from 'vite-plugin-cesium'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [cesium(), vue()],
})

启动没有错误,打开页面提示没有找到css文件

warnings emitted when using Node 20.9.0 and yarn 3.2.4

If I do:

  1. mkdir test
  2. cd test
  3. yarn init
  4. yarn add vite cesium rollup
  5. yarn add vite-plugin-cesium

I get the following warnings:

➤ YN0061: │ sourcemap-codec@npm:1.4.8 is deprecated: Please use @jridgewell/sourcemap-codec instead
➤ YN0002: │ vite-plugin-cesium@npm:1.2.22 [57297] doesn't provide rollup (pa143a), requested by rollup-plugin-external-globals

It would be nice if these warnings could be dealt with so they do not interfere noticing warnings that are important.

I am assuming these warnings are not pointing to a serious problem. Can you confirm?

构建时cesium路径错误,导致copy到dist文件夹下失败

大佬,您好,我再yarn build的时候发现提示报错,查看原因发现是cesium文件夹copy到dist目录下失败,预览这块是没问题,通过代码走查,发现是由下面这段代码会引起错误
image
如果注销掉60行代码后,就能正常打包,或者把join改成resolve也可以正常打包
由于是第一次接触vite,没有vite插件开发经验,只能先给您提出来,期待您的优化
开发环境是window

你好 添加地形后,地球消失

你好 添加地形后,地球消失。原始的cesium加载同样的数据是可以正常显示的。技术路线 vite+vue3+vite-plugin-cesium[cesiumlab处理的tif叠加后地球不显示]。vue2+cesium 【同样数据是可以显示的】

构建cesium文件路径异常

构建的时候,cesium文件夹变成了根目录,不再打包文件dist下面,这个会导致线上找不到Cesium.js

sourcemap-codec@npm:1.4.8 is deprecated: Please use @jridgewell/sourcemap-codec instead

I am working on upgrading a project to node 20.9.0 and yarn 3. This warning was emitted and it appears your package is the reason why -- according to yarn why.

$ yarn why sourcemap-codec -R                                                       

yarn why v1.22.19
[1/4] 🤔  Why do we have the module "sourcemap-codec"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found "[email protected]"
info Reasons this module exists
   - "vite-plugin-cesium#rollup-plugin-external-globals#magic-string" depends on it
   - Hoisted from "vite-plugin-cesium#rollup-plugin-external-globals#magic-string#sourcemap-codec"
info Disk size without dependencies: "68KB"
info Disk size with unique dependencies: "68KB"
info Disk size with transitive dependencies: "68KB"
info Number of shared dependencies: 0
✨  Done in 1.26s.

It would be nice if this deprecation warning could be fixed.

怎样调试呢?

请问通过这种构建出cesium环境后,应该怎样在浏览器的调试界面下进行调试呢?
比如在渲染过程中,怎么看cesium内部的相关变量的值(如framestate.commandList)

App cannot locate cesium resources

I have a GitHub repo at my-vue-app--use-plugin branch which demonstrates the problem.

I am able to build and run the app, but I am receiving a bunch of errors in the console like

bingAerial.png:1     Failed to load resource: the server responded with a status of 404 (Not Found)
bingAerialLabels.png:1     Failed to load resource: the server responded with a status of 404 (Not Found)

which are cesium resources.

I have my vite.config.js file written as:

import { defineConfig } from 'vite'
import { join } from 'path';
import serveStatic from 'serve-static';
import path from 'path';
import cesium from 'vite-plugin-cesium';

import vue from '@vitejs/plugin-vue'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [
    vue(),
    cesium()
  ],
})

and my package.json contains the expected packages.

Any idea what is going wrong?

no such file or directory, scandir dist

vite5 vue3 import vite-plugin-cesium": "^1.2.22,and vite.config.ts add code

import cesium from "vite-plugin-cesium";
const plugins = []
plugins.add(cesium ())

and vite is ok, but vite build throw error,

[Error: ENOENT: no such file or directory, scandir 'dist'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'scandir',
  path: 'dist'
}

it had transformed done, but write dist throw error, but not import vite-plugin-cesium and dist will auto generator

use vite-plugin-cesium start project has error: Invalid define value (must be valid JSON syntax or a single identifier): /cesium/

leo@leodeMacBook-Pro AESA-Visual-System % yarn dev
yarn run v1.22.10
warning package.json: No license field
$ vite
Pre-bundling dependencies:
vue
vuex
vue-router
cesium
(this will be run only when your dependencies or config have changed)

error: Invalid define value (must be valid JSON syntax or a single identifier): /cesium/

error when starting dev server:
Error: Build failed with 1 error:
error: Invalid define value (must be valid JSON syntax or a single identifier): /cesium/
at failureErrorWithLog (/Users/leo/Desktop/leixiang/workspace/AESA-Visual-System/node_modules/esbuild/lib/main.js:1224:15)
at buildResponseToResult (/Users/leo/Desktop/leixiang/workspace/AESA-Visual-System/node_modules/esbuild/lib/main.js:936:32)
at /Users/leo/Desktop/leixiang/workspace/AESA-Visual-System/node_modules/esbuild/lib/main.js:1035:20
at /Users/leo/Desktop/leixiang/workspace/AESA-Visual-System/node_modules/esbuild/lib/main.js:568:9
at handleIncomingPacket (/Users/leo/Desktop/leixiang/workspace/AESA-Visual-System/node_modules/esbuild/lib/main.js:657:9)
at Socket.readFromStdout (/Users/leo/Desktop/leixiang/workspace/AESA-Visual-System/node_modules/esbuild/lib/main.js:535:7)
at Socket.emit (events.js:315:20)
at addChunk (internal/streams/readable.js:309:12)
at readableAddChunk (internal/streams/readable.js:284:9)
at Socket.Readable.push (internal/streams/readable.js:223:10)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Vite 2.8.6下引入报错

使用Vite创建项目,引入vite-plugin-cesium, 然后运行出现如下错误:
failed to load config from D:\code\html\vite-project\vite.config.ts
error when starting preview server:
TypeError: cesium is not a function
at file:///D:/code/html/vite-project/vite.config.ts.js?t=1647506660917:6:13
at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
at async Promise.all (index 0)
at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15)
at async loadConfigFromFile (D:\code\html\vite-project\node_modules\vite\dist\node\chunks\dep-9c153816.js:71326:31)
at async resolveConfig (D:\code\html\vite-project\node_modules\vite\dist\node\chunks\dep-9c153816.js:70873:28)
at async preview (D:\code\html\vite-project\node_modules\vite\dist\node\chunks\dep-9c153816.js:69518:20)
at async CAC. (D:\code\html\vite-project\node_modules\vite\dist\node\cli.js:783:24)

dev environment won't start

Thank you for creating this plugin, however it seems like it's not working.
current stack is

  1. vite2,
  2. react,
  3. tailwindcss,
  4. typescript,
  5. vite-plugin-cesium

running in dev mode, which is a simple "vite" call.

the server is stuck at loading and the tab needs to be closed and reopened. Attached is a sample project showing this issue
frontend.zip

perform a build and previewing the result works fine however.

npm run build
npm run preview

My guess is there is an issue in the call

async closeBundle() { ... }

operating system ubuntu 20 LTS

Option to not inject `.css` in `index.html` during build

Thanks for a great vite plugin. 👏

When using cesium.js in a lazy loaded JavaScript bundle, cesium({ rebuildCesium: true }) works well since

if (isBuild && !rebuildCesium) {
tags.push({
tag: 'script',
attrs: {
src: normalizePath(path.join(CESIUM_BASE_URL, 'Cesium.js')),
}
});
}
ensures the <script...> tag is not included in the index.html, and therefore also cesium.js (which is quite large in size) is not loaded when visiting the main entrypoint of the application.

I think it would be beneficial to also have the plugin option to not inject the stylesheet link, i.e.

transformIndexHtml() {
const tags: HtmlTagDescriptor[] = [
{
tag: 'link',
attrs: {
rel: 'stylesheet',
href: normalizePath(path.join(CESIUM_BASE_URL, 'Widgets/widgets.css')),
}
}

Use case arguments:

  1. When lazy loading cesium.js, it would be nice to also lazy load the associated cesium CSS file, which is quite large (30 kB) and unhashed (i.e. can't be cached safely). For projects who want to lazy load the .css this is easily accomplished by importing the css as well
    import "cesium/Build/Cesium/Widgets/widgets.css";
    in the source code where import * as Cesium from "cesium"; is already imported (maybe adding this assoicated css import can even be done automatically by the vite plugin when rebuildCesium: true, before vite/rollup do their bundling?). The required cesium .css then goes through all the vite machinery for minimizing/lazy-chunking it...
  2. ...which then also puts it into a hashed file, which ensures the cesium css can also be strongly cached, instead of having to load it every time (without hash you would have problems when updating cesium later).

Current "workaround" is to remove the injected <link rel="stylesheet" href="/cesium/Widgets/widgets.css"> line in the generated index.html, and instead ensure the .css is added to the vite generated .css bundle by adding import "cesium/Build/Cesium/Widgets/widgets.css";

最新版本的cesium报错

博主这个库很棒,但是最近升级cesium的时候遇到了问题,引入最新版本的cesium报错,cesium版本1.104.0,报错如图:
WX20230427-093618@2x

earthsdk

can setting a option to use earthsdk

Demo didn't build

What I tried doing was:

  1. git clone [email protected]:nshen/vite-plugin-cesium.git
  2. cd vite-plugin-cesium/demo
  3. yarn
  4. yarn dev

The error output I received was:

(lm_env) ~/d/v/t/v/demo (main|✔) $ yarn dev                                                                                                                                                         14:27:14
yarn run v1.22.19
$ vite
✘ [ERROR] [plugin externalize-deps] Failed to resolve entry for package "vite-plugin-cesium". The package may have incorrect main/module/exports specified in its package.json.

    node_modules/esbuild/lib/main.js:1336:27:
      1336 │         let result = await callback({
           ╵                            ^

    at packageEntryFailure (file:///Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/vite/dist/node/chunks/dep-5605cfa4.js:34107:11)
    at resolvePackageEntry (file:///Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/vite/dist/node/chunks/dep-5605cfa4.js:34104:5)
    at tryNodeResolve (file:///Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/vite/dist/node/chunks/dep-5605cfa4.js:33842:20)
    at file:///Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/vite/dist/node/chunks/dep-5605cfa4.js:63090:40
    at requestCallbacks.on-resolve (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:1336:28)
    at handleRequest (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:706:19)
    at handleIncomingPacket (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:728:7)
    at Socket.readFromStdout (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:656:7)
    at Socket.emit (node:events:513:28)
    at addChunk (node:internal/streams/readable:315:12)

  This error came from the "onResolve" callback registered here:

    node_modules/esbuild/lib/main.js:1260:20:
      1260 │       let promise = setup({
           ╵                     ^

    at setup (file:///Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/vite/dist/node/chunks/dep-5605cfa4.js:63080:27)
    at handlePlugins (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:1260:21)
    at buildOrServeImpl (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:951:5)
    at Object.buildOrServe (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:759:5)
    at /Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:2096:17
    at new Promise (<anonymous>)
    at Object.build (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:2095:14)
    at build (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:1942:51)
    at bundleConfigFile (file:///Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/vite/dist/node/chunks/dep-5605cfa4.js:63043:26)

  The plugin "externalize-deps" was triggered by this import

    vite.config.ts:2:19:
      2 │ import cesium from 'vite-plugin-cesium';
        ╵                    ~~~~~~~~~~~~~~~~~~~~

failed to load config from /Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/vite.config.ts
error when starting dev server:
Error: Build failed with 1 error:
node_modules/esbuild/lib/main.js:1336:27: ERROR: [plugin: externalize-deps] Failed to resolve entry for package "vite-plugin-cesium". The package may have incorrect main/module/exports specified in its package.json.
    at failureErrorWithLog (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:1575:15)
    at /Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:1033:28
    at runOnEndCallbacks (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:1447:61)
    at buildResponseToResult (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:1031:7)
    at /Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:1143:14
    at responseCallbacks.<computed> (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:680:9)
    at handleIncomingPacket (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:735:9)
    at Socket.readFromStdout (/Users/eric/depot/vue/thirdparty/vite-plugin-cesium/demo/node_modules/esbuild/lib/main.js:656:7)
    at Socket.emit (node:events:513:28)
    at addChunk (node:internal/streams/readable:315:12)

Perhaps I missed a step?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.