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

eksi-sozluk

v5.0.1

Published

Eksi Sozluk NodeJS client.

Downloads

41

Readme

🍋 Unofficial Ek$i Sozluk Client for Node.js

npm version npm downloads Commitizen friendly semantic-release Build Status Coverage Status license

This library help you to conquer the Eksi Sozluk in Node.js.

Table of Contents

Installation

npm install eksi-sozluk --save

Documentation

Technical documentation is automatically created with JSDoc after each new release.

You can find the technical documentation here!

Tutorials

IMPORTANT: The tutorials are not fully covered for all use cases and its not mention all capabilities of the library, don't forget to check technical documentation if you didn't found anything you looking for.

Development

# clone the repository
git clone https://github.com/ridvanaltun/eksi-sozluk.git

# go to the project and install dependencies
cd eksi-sozluk & npm i

After these steps you can change the code. If you want test your changes; go to __tests__ folder, find a proper test file or create one if necessary. if the test pass, ensure your code quality and write documentation. All after you are ready to send a PR.

Check scripts section to learn how to run tests and linter (for code quality).

Commit Messages

Every commit message must be conventional commits format.

What is Conventional Commits?

If you don't have a time just use npm run commit command instead of use Git.

Code Quality

Keeping code quality as good is a hard job in normally. Therefore, we are using EsLint (linter) and Prettier to keep and track the code quality. Not linted pull requests automatically deny from via Travis (CI/CD). You can lint your code using scripts section.

In short, run npm run lint command.

Available Scripts

# commit your changes with commitizen
npm run commit

# check linter and prettier errors, fix prettier errors in default
npm run lint

# check the linter and prettier errors
npm run lint:check

# run prettier
npm run format

# check prettier errors
npm run format:check

# run all tests
npm run test

# travis uses this script, it handles creating new releases
npm run semantic-release

# travis uses this script, it creates documentation with jsdoc
npm run docs

Special Thanks

I would like to thank @kucukkanat the owner original eksi-sozluk package for transferring the package's rights to me. The old package was in security holding status, nobody was using it.

License

GNU General Public License v3.0