Update: it seems like the errors in the latter two pages below are due to an ill-advised NODE_PATH=. in my dotfiles.
The first page, showing how long it takes for react-plotly.js to lazily load (after initial page render) still makes sense, and a "production version" can be seen here: runsascoded.com/plotly-next-test.
Boot dev mode:
next devVisit:
- 127.0.0.1:3000:
- Renders a plot, though
react-plotly.jsis loaded asynchronously after the rest of the page - See pages/index.js
- Renders a plot, though
- 127.0.0.1:3000/to-image
- Attempts to lazily import
plotly.js(per docs example) - Errors while importing this line in
nodeca/probe-image-size@7.2.3/lib/parse_stream/avif.js require('probe-image-size/lib/common')returns an empty object
- Attempts to lazily import
- 127.0.0.1:3000/probe-image-size-import
- Simplest example: page fails to load due to (unused)
import common from "probe-image-size/lib/common"
- Simplest example: page fails to load due to (unused)