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

anlam

v1.0.1

Published

Sözcüksel ve istatistik tabanlı morfolojik Türkçe doğal dil işleme kütüphanesi.

Downloads

3

Readme

Build Status Dependencies devDependency Status

anlam

Webpack starter kit for creating libraries (Input: ES6, Output: UMD, CommonJS)

Features

Getting started

1. Setup the library's name

  • Open webpack.config.js and change the value of libraryName variable with your library's name.
  • Open package.json and change the following properties with your library's equivalent
    • name
    • version
    • description
    • main
    • repository
    • author
    • license
    • bugs
    • homepage

2. Install dependencies

  • Run npm install to install the library's dependencies.

3. Build for development

  • Having all the dependencies installed run yarn dev. This command will generate a UMD unminified bundle under the dist folder and a CommonJS bundle under the lib folder. It will also watch for changes in source files to recompile.

4. Build for production

  • Having all the dependencies installed run yarn build. This command will generate two UMD bundles (unminified and minified) under the dist folder and a CommonJS bundle under the lib folder.

Scripts

  • yarn build - Produces production version of library under dist folder for UMD bundle and lib folder for CommonJS bundle.
  • yarn build:umd - Produces an unminified UMD bundle under the dist folder.
  • yarn build:umdmin - Produces an minified UMD bundle under the dist folder.
  • yarn build:commonjs - Produces a CommonJS bundle under the lib folder.
  • yarn dev - Produces a development version of library (both UMD and CommonJS) and runs a watcher to watch for changes.
  • yarn dev:umd - Produces an unminified UMD bundle under the dist folder and runs a watcher to watch for changes.
  • yarn dev:commonjs - Produces a CommonJS bundle under the lib folder and runs a watcher to watch for changes.
  • yarn test - Runs the tests.
  • yarn coverage - Runs the tests and provides with test coverage information.
  • yarn lint - Lints the source code with ESlint.
  • yarn clean - Deletes dist, lib and coverage folders.
  • yarn prepare - Run both BEFORE the package is packed and published, on local npm install without any arguments, and when installing git dependencies.

License

MIT License