npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

tauri-logger

v1.0.5

Published

Log critical actions through your frontend like you would do with console.log and store them locally!

Downloads

7

Readme

Log critical actions through your frontend like you would do with console.log and store them locally!

IMPORTANT! Don't forget to set your scopes:

If you use the default dir-name option (see below)


"tauri": {
        "allowlist": {
		"fs": {
			"createDir": true,
			"writeFile": true,
			"scope": ["$DOCUMENT/YOURAPPNAME/logs"]
			}
		}
}

Or if you use a custom dir name you will have to change the YOURAPPNAME accordingly

"scope": ["$DOCUMENT/YOURCUSTOMDIRNAME/logs"]

This can be utilized to write logs of certain specified actions:

function criticalFunction() {
	try {
		tauriLog("critical function success")
	}
	catch (e)
		tauriLog("Crashed: " e)
}

To use the logger, place the function

initializeLogger()

inside your index.js/ts file

Then use

tauriLog(action)

whenever you want to log something

Errors produced by your frontend are logged automaticly unless you set the option to false

initializeLogger({
	reportErrors: false
})

A DiagnosticReport is also included by default unless turned off (includes appName, appVersion and the used tauriVersion)

initializeLogger({
	diagnosticReport: false
})

The default directory where the logs are stored is the Document folder, inside which a directory with you app name will be created

The app name is retrieved from the config file created by tauri

Example:

"package": {
        "productName": "your-appname",
    },

You can also set a custom dir that will be created in the Document Folder

initializeLogger({
	customDirName: "yourDirName"
})

If you encounter any problems or want to contribute feel free to do so!!!

Github Repo