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

cwel

v0.1.0

Published

Countrywide Experience Language

Downloads

3

Readme

Countrywide Experience Language (CWEL)

Welcome to CWEL, a front-end framework and experience language for the web.

Setup instructions

Setup involves a set of gulp commands:

  • Active development: gulp watch to get the sandbox and documentation page up.
  • Build: gulp build to build the entire project.
  • Lint: gulp lint to lint the SCSS and JS in this project.
    • gulp lint:script to only lint the JS
    • gulp lint:style to only lint the SCSS
  • Test
    • unit (karma): gulp test-unit
    • end to end (protractor): gulp test-e2e
    • visual (galen): gulp test-visual

Steps

  1. run npm install in your command line
  2. run gulp build to build the whole project
    • it might be necessary to install gulp globally: npm install -g gulp if an error occurs.

Contributing

For any pull requests to be accepted, the following guidelines must be followed. These cover code style and methodologies. Suggested tooling is listed at the end to help follow these guides.

Note: Tildes (~) in paths like ~/package.json denote the project's root folder.

Filenames

Make sure all filenames in this project adhere to kebab case. Exceptions to this are ~/LICENSE and ~/README.md to make them stand-out.

Create something

To create something for CWEL, read how to create something. This covers the steps necessary to contribute source code.

Code styleguides

Use eslint and stylelint to ensure your code style generally conforms with the project's standards; see setup instructions above for lint commands.

SCSS styleguide

Some things are not caught by linters, so please read the scss styleguide and for clarification.

JS styleguide

These are all covered by eslint.

Sandbox pages

To work on the CWEL library or experiment with new ideas, sandbox pages can be made. To do so, follow the steps outlined in the sandbox readme.

Documenation pages

To document new components, or any piece of CWEL, documentation pages can be written. For instuctions, read the readme for documentation pages.

To do

For a list of miscellaneous tasks, see the todo readme.