Jack Rowlingson

I am seeing a similar result as @btecu when using the `index.js` approach described in the docs. Here, I am setting `plugins` so that it is not empty. I was...

@achambers I believe the PR above should resolve this.

This would be a nice addition.

A [lazy loading approach](https://www.ioannispoulakas.com/2020/02/22/how-to-speed-up-shell-load-while-using-nvm/) can be used as a work around if you're seeing lag before the prompt becomes usable. The following can be added to your `.zshrc` (or `.*rc`):...

I've since switched node version managers (`fnm`). Offering this as a workaround for folks seeking help and finding this issue.

Node10 resolution will not resolve the newer `exports` package entry point. > For new packages targeting the currently supported versions of Node.js, the ["exports"](https://nodejs.org/docs/latest-v18.x/api/packages.html#exports) field is recommended. [[1](https://nodejs.org/docs/latest-v18.x/api/packages.html#package-entry-points)]

@rwaskiewicz :+1: - fwiw, I ran into this after creating a package for some common utils and found I was unable to use the "exports" package entry point (recommended).

@rwjblue This _does_ look amazing - any updates?