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

Module parse failed: Unexpected token #8

Open
marcosrjjunior opened this issue Aug 24, 2024 · 1 comment
Open

Module parse failed: Unexpected token #8

marcosrjjunior opened this issue Aug 24, 2024 · 1 comment

Comments

@marcosrjjunior
Copy link

  • Issue happening after updating from "^0.3.0" to "^0.4.1",

Error:

 ⨯ ./node_modules/.pnpm/@[email protected]/node_modules/@libsql/client/README.md
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <p align="center">
|   <a href="https://docs.turso.tech/sdk/ts/quickstart">
|     <img alt="Turso + TypeScript" src="https://github.com/tursodatabase/libsql-client-ts/assets/950181/5d3a2693-75f9-4c56-9107-8ccaa96785fd" width="1000">

Import trace for requested module:
./node_modules/.pnpm/@[email protected]/node_modules/@libsql/client/README.md
./node_modules/.pnpm/[email protected]/node_modules/@libsql/ ./node_modules/.pnpm/node_modules/@libsql/ ./node_modules/@libsql/ ./node_modules/.pnpm/node_modules/@libsql/ ./node_modules/.pnpm/[email protected]/node_modules/@libsql/ ./node_modules/.pnpm/node_modules/@libsql/ ./node_modules/@libsql/ ./node_modules/.pnpm/node_modules/@libsql/ sync ^\.\/.*$
./node_modules/.pnpm/[email protected]/node_modules/libsql/index.js
./node_modules/.pnpm/@[email protected]/node_modules/@libsql/client/lib-esm/sqlite3.js
./node_modules/.pnpm/@[email protected]/node_modules/@libsql/client/lib-esm/node.js
./node_modules/.pnpm/@[email protected][email protected]/node_modules/@libsql/kysely-libsql/lib-esm/index.js

might be related to:

environment

  • "next": "14.2.5",
@ottomated
Copy link
Contributor

ottomated commented Aug 28, 2024

This is definitely an upstream issue because 0.4.1 now depends on @libsql/client, the issue you linked seems like the root cause.

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

No branches or pull requests

2 participants