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

mlscript

v0.0.1-beta.5

Published

mlscript

Downloads

12

Readme

MLscript

This is a pre-release of MLscript.

Quick Start

To install MLscript, you can use npm:

npm i mlscript

The newest version is recommended: there may be lots of bugs in the previous versions.

To watch the project directory, you can use TypeScript(recommended)/JavaScript:

import mlscript from "mlscript"

// filename: string, workDir: string, outputDir: string, tsconfig: string, commonJS: boolean, expectTypeError: boolean
mlscript.watch("./mlscript/Main.mls", "./", "./js/", "./tsconfig.json", false, true)

The path must start with ./, or it will be treated as node_modules paths.

If you need to interoperate with TypeScript, you must provide the path of tsconfig.json file. Otherwise, it is optional.

You can choose to use CommonJS or ES modules(recommended).

Since Mlscript is still under development, type inferences are not fully supported. If there is a type error but it is correct, please set the expectTypeError flag to true. To get the type error messages, please check the corresponding .mlsi files in .interfaces.

For more details, you can check the demo here.

Project Structure

The MLscript uses git to track the file changes. Please make sure your project locates in a git repo.

Though not necessary, we still recommend you organize the project in this structure:

  • .interfaces: temporary interface files generated by MLscript.
  • mlscript: directory for MLscript files.
  • node_modules: third-party libraries in TypeScript.
  • ts: directory for TypeScript files.
  • configuration files: package.json and tsconfig.json should locate in the root directory.