You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
recently i found tauri, and try to migrate my project to tauri and found a convenient features that tauri is not have,that propagation request to it's host when using native request.
eg:
// in native ios emulator:fetch('localhost:1420/api/endpoint')// it will forward this request to laptop's localhost:1420/api
// and in vite config.ts or some other proxy tools already define proxy likeserver: {proxy: {'/api': {target: 'http://127.0.0.1:3000',changeOrigin: true,rewrite: (path)=>path.replace(/^\/api/,''),},},},
would consider add it into tauri,otherwise, when i start dev the project if my laptop ip change,i need change ip each time.
if support visit emulator localhost it will propagation to it's host,i may use localhost when dev, and use some hostname in production.
Describe the solution you'd like
ionic-team/capacitor#6388 like this issue have some valuable info,that user can visit emulator localhost to visit it's host
capacitor http request request localhost and it's have response
Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the problem
recently i found tauri, and try to migrate my project to tauri and found a convenient features that tauri is not have,that propagation request to it's host when using native request.
eg:
would consider add it into tauri,otherwise, when i start dev the project if my laptop ip change,i need change ip each time.
if support visit emulator localhost it will propagation to it's host,i may use localhost when dev, and use some hostname in production.
Describe the solution you'd like
ionic-team/capacitor#6388 like this issue have some valuable info,that user can visit emulator localhost to visit it's host
capacitor http request request localhost and it's have response
Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: