Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Having an error with NodeJS 17 #405

Closed
aliasad106 opened this issue Oct 29, 2021 · 5 comments
Closed

Having an error with NodeJS 17 #405

aliasad106 opened this issue Oct 29, 2021 · 5 comments

Comments

@aliasad106
Copy link

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './public/extractFiles' is not defined by "exports" in /Users/aliasadullah/leafappio/node_modules/extract-files/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/aliasadullah/leafappio/node_modules/apollo-upload-client/public/createUploadLink.js:18:20) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

@parse-github-assistant
Copy link

parse-github-assistant bot commented Oct 29, 2021

Thanks for opening this issue!

  • ❌ Please edit your post and use the provided template when creating a new issue. This helps everyone to understand your post better and asks for essential information to quicker review the issue.

@aliasad106 aliasad106 changed the title Having an error with Node 17 Having an error with NodeJS 17 Oct 29, 2021
@7aklhz
Copy link

7aklhz commented Nov 3, 2021

same issue

@cbaker6
Copy link

cbaker6 commented Nov 10, 2021

I recommend keeping an eye on the parse-server issues: parse-community/parse-server#7686

And check the readme for versions the parse-server is currently compatible with (it currently shows Node 12,14, and 15): https://github.com/parse-community/parse-server. I advise only updating when the README shows a version is compatible or else you are entering untested territory...

@aacassandra
Copy link

node 16 same error

@dblythy
Copy link
Member

dblythy commented Apr 1, 2022

Please have a look at Parse Server's compatibility

Issues with Parse Server should be opened in the Parse Server Repo.

Here is issue tracking Node 17 compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants