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

tscw

v0.1.2

Published

Typescript watch compiler - temporary hotfix for -w parameter on node.js

Downloads

19

Readme

Typescript watch compiler

The current typescript's implementation of -w parameter is broken. Here's a little utility to fix that.

Usage

Normal usage::

npm install -g tscw
tscw <parameters which you would use with tsc>

The parameters which you pass to tscw are transparently sent to tsc compiler.

TSCW does only one thing - watches for file changes and compiles (correctly) as it would under normal conditions. Problem solved. Temporarily.

Debugging of .ts files

On some platforms (definitely on Windows + node.js stack), there might be tsc command output stripped when invoked from external tools, like tscw. This results into the fact that development, as easied by tscw utility, will be much harder. This is caused by this bug_.

The result is not-to-be-seen at first glance. Generally, you will see where the compilation stopped, but sometimes you might not see the reason for your .ts file not compiling. This is just wrong. Consider this output of tscw:

.. image:: https://raw.github.com/foglcz/pull-support/master/tscw/with-bug.png

Not much information, right? In order to fix it, update your tsc.js file (found in AppData/npm/node_modules/typescript on windows stack). Find the line (21 267), which reads::

quit: process.exit

And replace it with following code::

quit: function (exitCode) {
          if (typeof exitCode === "undefined") { exitCode = 0; }
          process.on('exit', function () {
              process.exit(exitCode);
          });
      }

The full diff of tsc.js file can be found here_.

If implemented correctly, the message will be fixed into this:

.. image:: https://raw.github.com/foglcz/pull-support/master/tscw/without-bug.png

That's better, right?

.. _bug: http://typescript.codeplex.com/SourceControl/network/forks/foglcz/typescript/contribution/3532 .. _here: https://gist.github.com/0d34d8fe3da0c02777c1

Author & License

Created -w love by Pavel Ptacek, licensed under WTFPL license. Full license can be found here: http://sam.zoy.org/wtfpl/COPYING

note: The WTFPL license means, that you can do whatever you want with the tscw package.