You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Step 1: install metascraper and metascraper-image packages
Step 2: use it somewhere in a nuxt project. in the reproduction provided, i made a "link-preview" endpoint.
Step 3: build
For some reason it happens specifically on my machine only.
I tried building on a server and github action environment and on codesandbox and they all build as expected like on the "previous" i.e no canvas in .output/server/node_modules.
I'm not sure what change caused this because I don't have any AFAIK.
Doesn't seem to be code issue though cause it work on other environment.
On the other hand, upon checking jsdom's README, I think it shouldn't have the package installed or even bundled unless you have it in your own project's dependencies.
Environment
Nuxt project info: 5:24:41 am
Reproduction
Reproduction: https://codesandbox.io/p/devbox/nuxt-jsdom-canvas-4wgflf
Repo: https://github.com/xxRockOnxx/nuxt-issue
Step 1: install
metascraper
andmetascraper-image
packagesStep 2: use it somewhere in a nuxt project. in the reproduction provided, i made a "link-preview" endpoint.
Step 3: build
Describe the bug
I use the packages metascraper and metascraper-image to create a "link preview" api endpoint.
Somewhere in its dependency chain is jsdom which includes canvas as its peer dep.
For some reason, suddenly, I now get giant build output.
I checked using
du -h .output/server | sort -h
for the biggest file/folder, I saw the following:as opposed to the previous:
For some reason it happens specifically on my machine only.
I tried building on a server and github action environment and on codesandbox and they all build as expected like on the "previous" i.e no
canvas
in.output/server/node_modules
.I'm not sure what change caused this because I don't have any AFAIK.
Doesn't seem to be code issue though cause it work on other environment.
On the other hand, upon checking jsdom's README, I think it shouldn't have the package installed or even bundled unless you have it in your own project's dependencies.
I'm lost here. Any clues?
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: