@theholocron/klaxon

Klaxon

Klaxon is the loudest way to debug within the Galaxy.

Installation

npm install --save @theholocron/klaxon

Table of Contents

• Usage
• Browsers & Devices
• Documentation
• Changelog
• Versioning
• Contribution
• Support
• Tools
• Support
• License

Usage

This is meant to be a wrapper around console API with some helper methods for formatting.

import echo from '@theholocron/klaxon';

echo.log('This is a message');
echo.info('This is a message with info level status');
echo.warn('This is a message with warning level status');
echo.error('This is a message with error level status');
echo.log(echo.asAlert('This is a message that will look like an alert'));
echo.log(echo.asInfo('This is a message that will look like an alert'));
echo.log(echo.asProcess('This is a message that will look like its processing'));
echo.log(echo.asSuccess('This is a message that will look sucessful'));
echo.log(echo.asWarning('This is a message that will look like a warning'));

Which Browsers & Devices We Support

We support the latest, stable releases of all major browsers and platforms based on the most common usage from stats accumulated in Google Analytics. We use caniuse.com programmatically to determine support and browserl.ist to determine usage based on strings we provide. This technically translates to the > ~0.03% in my stats, excluding IE11 and Opera Mini using not ie 11, not op_mini all.

IE / Edge	Firefox	Chrome	Safari	iOS Safari	Opera
Edge	last 10 versions	last 8 versions	last 2 versions	last 2 versions	last 2 versions

Alternative browsers which use the latest version of WebKit, Blink, or Gecko, whether directly or via the platform's web view API, are not explicitly supported. However, it should (in most cases) display and function correctly in these browsers as well. More specific support information is provided below.

Where to Find Documentation

The best way to find out what's available is to check out the source code or test but you can also take a look at the-holocron.github.io/klaxon or the README which have been generated by SassDoc and sassdoc-to-markdown.

How We Track Changes

This project uses a CHANGELOG and GitHub releases which contains a curated, chronologically ordered list of notable changes for each version of a project. Read more about changelogs.

How We Version

We use SemVer for its versioning providing us an opt-in approach to releases. This means we add a version number according to the spec, as you see below. So rather than force developers to consume the latest and greatest, they can choose which version to consume and test any newer ones before upgrading. Please the read the spec as it goes into further detail.

Given a version number MAJOR.MINOR.PATCH, increment the:

• MAJOR version when you make incompatible API changes.
• MINOR version when you add functionality in a backward-compatible manner.
• PATCH version when you make backward-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

How to Contribute

Have a bug or a feature request? Looking to contribute to advance the project? Read our contribution guide or maintenance guide first in order to understand how we do things around here. Or you could look at some of our other guides below:

How do I… (click to expand)

• Ask or Say Something?
  • Request Support
  • Report an Error or Bug
  • Request a Feature
• Make Something?
  • Setup the Project
  • Create an Issue
  • Create a Feature Request
  • Contribute Documentation
  • Contribute Code
  • Join the Team
• Manage Something
  • Provide Support on Issues
  • Label Issues
  • Clean Up Issues and PRs
  • Create a Pull Request
  • Review Pull Requests
  • Merge Pull Requests
  • Tag a Release
  • Release a Version

💥 Interested in how we decide things? Check out our Mistakes We've Made document for an insight into the things we've considered.

Where to Find Support

Looking to talk to someone or need some help? Please read our support guidelines.

Tools We Use

• Browserslist - Used to share to our code which browsers we support
• Carbon - Used to generate the code examples in this README
• Conventional Changelog - Used to generate our CHANGELOG
• Husky - Used for auto-fixing linting errors on each commit
• Semantic Release - Used for automating and releasing our library
• @godban's Browser Support Badges - The tool used to generate the "Which Browsers [sic] We Support" section

References

• Conventional Commits - For how we format commit messages
• Contributor Convenant
• Keep a Changelog - For building out a quality CHANGELOG
• Make a README - For building out this README
• SemVer - For versioning this library

License

©2020 GNU General Public License v3. See LICENSE for specifics.