Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Package subpath './http' is not defined by "exports" in /workspace/node_modules/@sveltejs/app-utils/package.json

See original GitHub issue

It seems the latest version 1.0.0-next.1 changed the way it exports. It seems to be a problem with:

const {get_body: getBody} = require('@sveltejs/app-utils/http');

in handler.js

Issue Analytics

State:
Created 3 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

jthegeduscommented, Feb 11, 2021

When the node adapter moves it’s latest tag I will address this. https://www.npmjs.com/package/@sveltejs/adapter-node Screenshot from 2021-02-12 07-55-08

In the meantime, please use @sveltejs/kit@1.0.0-next.31, .33 may work, but I have not tested it

0reactions

github-actions[bot]commented, Mar 4, 2021

🎉 This issue has been resolved in version 0.3.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Top Results From Across the Web

Issues - GitHub

i18next-http-backend : Warning: Ignored package due to "Package subpath './package.json' is not defined by "exports"" ...

1 Answer - 1 - Stack Overflow

How to resolve Package subpath './package.json' is not defined by "exports" error · javascript · typescript · protractor · cucumberjs.

[err_package_path_not_exported]: package subpath './types ...

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/tokenize' is not defined by "exports" in the package.json of a module in node_modules.

Packages | Node.js v18 API

When the "exports" field is defined, all subpaths of the package are encapsulated and no longer available to importers. For example, require('pkg/subpath.js') ...

r/node - Reddit

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/tokenize' is not defined by "exports" in /root/.../package.json.