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

@lo1tuma/parallel-typescript

v0.0.7

Published

Not yet

Downloads

10

Readme

parallel-typescript

IT USES THE PRIVATE COMPILER'S API SO PLEASE DON'T USE IT IN PRODUCTION. IT'S JUST A POC!

This is a test repo of straightforward implementation of parallel compilation of TypeScript's composite projects.

It uses an idea that all independent sub-projects might be build in parallel in workers/different processes. It doesn't share state between sub-projects compilations (because it seems that compiler API doesn't support (de-)serialization of the state).

Example

Let's say you have solution with 4 projects, and dependency tree has the following structure:

   A
 /   \
B  C  D
 \ | /
   E

Here we can run in parallel compilation of B, C and D projects after E project is built. Thus you can run the following commands yourself:

tsc -b ./E

# run this ones in parallel
tsc -b ./B
tsc -b ./C
tsc -b ./D

# and run this one after all
tsc -b ./A

This is exactly what the tool does for you!

It relies that re-parsing (parsing/type-checking/etc) types from deps sub-projects and running in parallel might be faster than re-using types in the same thread/process and running compilation of all sub-projects sequentially. But I'm not sure about that (I'm looking for the project who can test it and compare the results) so we need to test it before using anywhere.