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
Hello!
First, thank you for this cool project, very nicely written and designed app!
No big deal really once you figure it out, but just thought I should share this here in case anyone experiences the same bug. When trying to build or start the dev server using a Node version > 16, it fails with the error listed in this StackOverflow post:
node:internal/modules/cjs/loader:488
throw e;
^
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/tokenize' is not defined by "exports" in /Users/juliantc/Desktop/ai-studio/development/frontend/node_modules/postcss-safe-parser/node_modules/postcss/package.json
at new NodeError (node:internal/errors:371:5)
at throwExportsNotFound (node:internal/modules/esm/resolve:416:9)
at packageExportsResolve (node:internal/modules/esm/resolve:669:3)
at resolveExports (node:internal/modules/cjs/loader:482:36)
at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:919:27)
at Function.Module._load (node:internal/modules/cjs/loader:778:27)
at Module.require (node:internal/modules/cjs/loader:999:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object.<anonymous> (/Users/juliantc/Desktop/ai- studio/development/frontend/node_modules/postcss-safe-parser/lib/safe-parser.js:1:17) {
code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
Not sure what the true fix would be, but if you're using some sort of node version manager (I use volta), an easy workaround is using node @ 16.x
The text was updated successfully, but these errors were encountered:
Hello!
First, thank you for this cool project, very nicely written and designed app!
No big deal really once you figure it out, but just thought I should share this here in case anyone experiences the same bug. When trying to build or start the dev server using a Node version > 16, it fails with the error listed in this StackOverflow post:
Not sure what the true fix would be, but if you're using some sort of node version manager (I use volta), an easy workaround is using node @ 16.x
The text was updated successfully, but these errors were encountered: