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.

Last build 0.3.22 Module not found

See original GitHub issue

after updating from 0.3.17 to 0.3.22 im getting the following error, its just me?

./node_modules/@usedapp/core/dist/esm/src/hooks/useGasPrice.js Module not found: Can't resolve '@usedapp/core/src/providers' in '/Users/brunitob/GitHub/koaladao-frontend/node_modules/@usedapp/core/dist/esm/src/hooks'

Issue Analytics

State:
Created 2 years ago
Comments:8 (3 by maintainers)

Top GitHub Comments

1reaction

mertzdevcommented, May 29, 2021

Similar issue here after upgrading to 0.3.22. Even with a completely fresh create-react-app once I import DAppProvider I get

Failed to compile.

./node_modules/@usedapp/core/src/providers/DAppProvider.tsx 13:0
Module parse failed: The keyword 'interface' is reserved (13: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
| import { TransactionProvider } from './transactions/provider'
| 
> interface DAppProviderProps {
|   children: ReactNode
|   config: Config

1reaction

stefanone91commented, May 29, 2021

me too! a simple “next.js” project with 0.3.22 won’t start because cannot compile… It seems like tsconfig.json inside “@usedapp/core” has an import of another tsconfig that is not present inside module folder.

EDIT: downgrade to 0.3.17 works for me

Top Results From Across the Web

install command doesn't work · Issue #8279 · google/jax - GitHub

Finally, I get ModuleNotFoundError: No module named 'jaxlib' when running import jax from a python prompt. I have CUDA 11.3 and cuDNN 8.2....

Module not found: Error: Cannot resolve module

In nodejs, when you call require("script1.js") it won't search in the current folder. You have to use require("./script2.js") , to specify ...

encountered error while generating package metadata

Ok, I faced this issue with python 3.10.4 and after searching I found two solutions for this problem because this problem not being...

The `wasm-bindgen` Guide - Rust and WebAssembly

Introduction. This book is about wasm-bindgen , a Rust library and CLI tool that facilitate high-level interactions between wasm modules and JavaScript.

wasm-bindgen-test 0.2.19 - Docs.rs

If you believe this is docs.rs' fault, open an issue. Visit the last successful build: wasm-bindgen-test-0.3.33. wasm-bindgen-test. This crate ...