-
Notifications
You must be signed in to change notification settings - Fork 165
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
Error under electron: Adapter 'http' is not available in the build #332
Comments
Seems already have a pull request here #314 |
Yes there's a branch that replaces axios with fetch, but haven't got round
to merging it yet. It would be great if you could test it i.e replace your
nano dependency with something like github.com/apache/couchdb-nano#fetch
…On Wed, 23 Aug 2023 at 07:56, Mario Valle ***@***.***> wrote:
Seems already have a pull request here #314
<#314>
—
Reply to this email directly, view it on GitHub
<#332 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFKMROWFWNAXLDWDSOP663XWWSTLANCNFSM6AAAAAA32636AQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
With pleasure, @glynnbird ! |
Dear @glynnbird , the modified version works perfectly (at least in my application)! |
I have the same error |
@MiniSuperDev The workaround until the nano package will be updated is to do:
Now magically the application works. |
Any news about merging the change in the main distribution? Waiting on the official release also because the suggested way to set options elicit an error in Typescript:
The strange error on
Thanks for looking! |
Expected Behavior
Used nano without errors under Node 20.4.0. I want to use the exactly same code under Electron that bundles Node 18.16.1
Current Behavior
At the first call to nano
I receive the error:
Seems the error is generated by
axios
and seems the solution is to move tofetch
. There is a possible workaround at axios/axios#5523 but settingagent
in therequestDefaults
has no effect.Possible Solution
Steps to Reproduce (for bugs)
npm run dev
Context
Well, this problem blocks entirely my porting of the client-server application under Electron.
If there is no solution I have to scrap CouchDB and move to another DB.
Your Environment
The text was updated successfully, but these errors were encountered: