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

@pikantino/compiler

v0.5.1

Published

Pikantino - Typescript & Angular compiler

Downloads

10

Readme

@pikantino/compiler

It's a tool to compile Typescript/Angular project into "ready-for-use" ES6 Modules. Uses @pikantino/pkg to compile dependencies. 1 second or less incremental builds irrespective of project complexity.

Installing

@pikantino/pkg is a peer dependency and should be installed manually.

  npm i @pikantino/pkg @pikantino/compiler --save-dev 

Usage

  1. (Optional) Create an additional index.html file to retain the possibility of ng builds.

  2. Add all of the polyfills to index.html as CDN links:

  <script src="https://cdnjs.cloudflare.com/ajax/libs/core-js/2.6.5/core.min.js"></script>
  <script src="https://cdnjs.cloudflare.com/ajax/libs/zone.js/0.8.29/zone.min.js"></script>
  1. Add entry point with type="module" and ".js" extension at the end of the body of index.html with a path relative to the root of the app:
  <script src="src/main.js" type="module"></script>
  1. Run pikantino-compiler (and pass the name of new index.html if it was created or run without any arguments)
  pikantino-compiler -i index.html
  1. Serve ./dist folder in any way (http-server might help).

You might also want to run tsc -w --noEmit to get types checked.

CLI

$ pikantino-compiler --help
Options:
  --version      Show version number                                   [boolean]
  --outDir, -o   Output directory                              [default: "dist"]
  --srcDir, -s   Sources directory                              [default: "src"]
  --modules, -m  Modules output directory               [default: "web_modules"]
  --tsconfig     TsConfig file path                   [default: "tsconfig.json"]
  --index        Index.html file path relative to your src folder
                                                         [default: "index.html"]
  --watch, -w    Watch changes and rebuild
  --help         Show help                                             [boolean]

Roadmap

  • [ ] Add lazy loading (SystemJS) setup guide
  • [ ] Add ability to pack dependencies that don't have ES6 build
  • [ ] Integrate serving tool and live reload
  • [ ] Integrate live type checking