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

@frontity/file-settings

v1.1.8

Published

A settings package for Frontity that uses a frontity.settings.js file.

Downloads

974

Readme

@frontity/file-settings

Version npm License: Apache--2.0

This is an internal package used by @frontity/core

A settings package for Frontity that reads a frontity.settings.js file.

frontity.settings.js should contain data that allows it to be serializable (as a JSON) so it can be stored in DB

Table of contents

Feature Discussions

Feature Discussions about Frontity are public. You can join the discussions, vote for those you're interested in or create new ones.

These are the ones related to this package: https://community.frontity.org/tags/c/feature-discussions/33/file-settings

Changelog

Have a look at the latest updates of this package in the CHANGELOG


Open Source Community

Channels

Community Forum Topics Twitter: frontity Frontity Github Stars

Frontity has a number of different channels at your disposal where you can find out more information about the project, join in discussions about it, and also get involved:

  • 📖 Docs: Frontity's primary documentation resource - this is the place to learn how to build amazing sites with Frontity.
  • 👨‍👩‍👧‍👦 Community forum: join Frontity's forum and ask questions, share your knowledge, give feedback and meet other cool Frontity people. We'd love to know about what you're building with Frontity, so please do swing by the forum and tell us about your projects.
  • 🐞 Contribute: Frontity uses GitHub for bugs and pull requests. Check out the Contributing section to find out how you can help develop Frontity, or improve this documentation.
  • 🗣 Social media: interact with other Frontity users. Reach out to the Frontity team on Twitter. Mention us in your tweets about Frontity and what you're building by using @frontity.
  • 💌 Newsletter: do you want to receive the latest news about Frontity and find out as soon as there's an update to the framework? Subscribe to our newsletter.

Get involved

GitHub issues by-label

Got questions or feedback about Frontity? We'd love to hear from you in our community forum.

Frontity also welcomes contributions. There are many ways to support the project! If you don't know where to start then this guide might help: How to contribute?.

If you would like to start contributing to the code please open a pull request to address one of our good first issues.