-
Notifications
You must be signed in to change notification settings - Fork 8
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
Compatibility with tauri-plugin-log
#150
Comments
Yeah okay so I played around with this somewhat yesterday and I really like your suggestion of making it compatible with the log plugins js functions. However, creating |
Okay so turns out I was overcomplicating things 😄 and adding compat with |
I have the same issue as @jeffgardnerdev. There doesn't seem to be a way to configure logs when this is added as a plugin. I have logs everywhere even in production so I get a lot of errors when I do not configure tauri_plugin_log. Neat tool you have here though. |
…patibility feat: compatibility with tauri-plugin-log, closes #150
The Tauri log plugin is widely used, but cannot coexist with devtools--this panic error crashes the app on startup when both plugins are added:
error while running tauri application: PluginInitialization("log", "attempted to set a logger after the logging system was already initialized")
This can be worked around by only adding the devtools plugin in development and only adding the log plugin in production, like so:
But this doesn't account for any log statements made on the JS side, like this:
Ideally there would be some way to seamlessly redirect log entries to devtools in development while retaining normal log plugin behavior in production.
The text was updated successfully, but these errors were encountered: