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

stencil-custom-typescript-output-target

v1.1.0

Published

StencilJS output target for compiling custom TypeScript in addition to your components

Downloads

3

Readme

stencil-custom-typescript-output-target

version license build

StencilJS output target for compiling custom TypeScript in addition to your components.

I had a situation where I wanted to compile some TypeScript, outside of the main Stencil component compile (some custom code I wanted incluided in my package).

This custom output target will make Stencil compile this code when it builds:

// stencil.config.ts
import { Config } from '@stencil/core';
import { compileCustomTypescriptOutputTarget } from 'stencil-custom-typescript-output-target';

export const config: Config = {
    // ... rest of your config
    outputTargets: [
        // ... your other output targets
        compileCustomTypescriptOutputTarget({
            tsconfigPath: 'custom.tsconfig.json',
        }),
    ],
};

Config

CompileCustomTsOptions: config object:

tsconfigPath: path to the tsconfig.json file to use. This should include or specify files. It should probably exclude your other Stencil code, so you're not building things twice / pulling in things you didn't mean to.

skipValidate: optional bool to skip the validate stage of the output target. This will mean any TS compiler errors will be allowed through without any issue.