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

Unable to resolve module url from node_modules/typeorm/browser/util/OrmUtils.js: url could not be found within the project. #6216

Closed
FottyM opened this issue Jun 6, 2020 · 6 comments

Comments

@FottyM
Copy link

FottyM commented Jun 6, 2020

Issue type:

[ ] question
[x] bug report
[ ] feature request
[ ] documentation issue

Database system/driver:

[ ] cordova
[ ] mongodb
[ ] mssql
[ ] mysql / mariadb
[ ] oracle
[ ] postgres
[ ] cockroachdb
[ ] sqlite
[ ] sqljs
[ ] react-native
[x] expo

TypeORM version:

[x] latest
[ ] @next
[ ] 0.x.x (or put your version here)

Steps to reproduce or a small repository showing the problem:

Unable to resolve module `url` from `node_modules/typeorm/browser/util/OrmUtils.js`: url could not be found within the project.

If you are sure the module exists, try these steps:
 1. Clear watchman watches: watchman watch-del-all
 2. Delete node_modules: rm -rf node_modules and run yarn install
 3. Reset Metro's cache: yarn start --reset-cache
 4. Remove the cache: rm -rf /tmp/metro-*

ABI37_0_0RCTFatal
__37-[ABI37_0_0RCTCxxBridge handleError:]_block_invoke
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_main_queue_callback_4CF
__CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
__CFRunLoopRun
CFRunLoopRunSpecific
GSEventRunModal
UIApplicationMain
main
start
@JoaoCRDias
Copy link

yarn add url solves this issue

@oleksandr-dziuban
Copy link

@Kolisium It should be added to typeorm dependencies then..

@oleksandr-dziuban
Copy link

oleksandr-dziuban commented Jun 11, 2020

Same issue here from version 0.2.25. Any react-native environment throws this error. Please check it

@maixuanhan
Copy link

I'm facing same issue with version 0.2.25
Version 0.2.0 was working fine

@Rafatcb
Copy link

Rafatcb commented Aug 6, 2020

Same issue as #6142, seems to be fixed in #6145

@imnotjames
Copy link
Contributor

Closing this as it's a duplicate of #6142

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

6 participants