https://github.com/userquin/vite-ssg-build-v-client-master

https://github.com/userquin/vite-ssg-build-v-client-master

Last synced: 15 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/userquin/vite-ssg-build-v-client-master
• Owner: userquin
• License: mit
• Created: 2022-05-05T12:10:30.000Z (over 2 years ago)
• Default Branch: master
• Last Pushed: 2022-05-05T12:16:40.000Z (over 2 years ago)
• Last Synced: 2024-10-15T00:02:21.103Z (about 1 month ago)
• Language: TypeScript
• Size: 82 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml
  • License: LICENSE

Awesome Lists containing this project

README

        
# [#230](https://github.com/antfu/vite-ssg/issues/230) vite-ssg minimal reproduction

This is just the [vitesse-lite](https://github.com/antfu/vitesse-lite) with `vite-ssg` installed and a few unnecessary things blown away.

## Problem

In `src/pages/index.vue` I am importing the esm output file of the `3d-force-graph` lib (unimportant). This has three.js as a dependency which uses window. 

> note: I am able to fully build this using `vite-ssg` if I import the UMD output file for `3d-force-graph` instead of `3d-force-graph/dist/3d-force-graph.module.js`.

The main problem now is that I would expect the `mock` flag in config to come to my aid when three.js (or whichever client side lib) tries to use `window`.

Am I misunderstanding the `mock` feature?

try: `pnpm build`