Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

fib-typify

Package Overview
Dependencies
Maintainers
1
Versions
33
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

fib-typify

just write fibjs with typescript : )

  • 0.4.1
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
77
increased by600%
Maintainers
1
Weekly downloads
 
Created
Source

fib-typify

NPM version Build Status Build status

just write fibjs with typescript : )

// entry.js
const vm = require('vm')
const typify = require('fib-typify')

typify.generateLoaderbox().require('./index.ts', __dirname)

// index.ts
export function foo (str: string): string {
    return `hello, ${str}`
}

Introduction

fib-typify allows you write fibjs with typescript in compilation or in runtime. It depends on original typescript stable version. As typescript is written with nodejs, it's not restricted in nodejs runtime: you can also compile typescript in browser or ANY other pure Javascript runtime. That is, you can use it in fibjs also.

renderer

fib-typify's core is jstransformer-typescript-like (jstransformer-typescript is one jstransformer aimed to typescript), but this core is only valid in fibjs rather than pure javascript

Usage

# locally
fibjs --install fib-typify
# or globally
npm i -g fib-typify

# compile code in ./src to ./dist recursively
fib-typify ./src -o ./dist

default tsCompilerOptions

internal default compilerOptions

{
    target: 'es6',
    module: 'commonjs',
    noImplicitUseStrict: true
}

tsconfig.json

Start from 0.4.0, compilerOptions from CWD/tsconfig.json would overwrite internal default compilerOptions.

priority of overwriting

  1. compilerOptions passed to function params
  2. compilerOptions in tsconfig.json
  3. internal default compilerOptions

APIs

NOTE All TSCompilerOptions is just typescript's compilerOptions


  • compileRaw: (tsRaw: string, tsCompilerOptions: TSCompilerOptions) => string

compile tsRaw to javascript.

  • compileRawToFile: (tsRaw: string, targetpath: string, tsCompilerOptions: TSCompilerOptions) => void

compile tsRaw to javascript, then write to targetpath.

  • compileFile: (filepath?: string, tsCompilerOptions: TSCompilerOptions) => string

compile content in filepath to javascript.

  • compileFileTo: (srcpath?: string, targetpath: string, tsCompilerOptions: TSCompilerOptions) => void

compile content in filepath to javascript, then write to targetpath.

  • compileDirectoryTo: (baseDir: string, distDir: string, directoryCompilationOptions: any) => void
ParamTypeRequired/Default
baseDirstringY / -
distDirstringY / -
directoryCompilationOptionsdirectoryCompilationOptionsN / -

compile files in directory baseDir recursively to distDir, view options in view directoryCompilationOptions.

  • generateLoaderbox(tsCompilerOptions: TSCompilerOptions, basedir: string)

generate one loaderBox with compilation options tsCompilerOptions.

  • registerTsCompiler(sandbox: vm.SandBox, tsCompilerOptions: TSCompilerOptions = defaultCompilerOptions)

register '.ts' compiler for one Sanbox which haven't been registered before.

  • loaderBox

default loaderBox of fib-typify, it use default tsCompilerOptions as compiler options for .ts.

  • defaultCompilerOptions

default typescript compiler options. More detail in typescript's compiler options


directoryCompilationOptions

FieldTypeRequired/DefaultExplanation
compilerOptionsbooleanY / falsetypescript's compilerOptions
fileglobsToCopyArray, '*'N / ['*.js', '*.jsc', '*.json']whitelist for extensions of globnames to copy when recursive walk to one
includeLeveledGlobsstringstring[]N / ['*', '!node_modules', '!.ts']
filterFileName(filename: string): booleanN / -whether compile File, file would be compiled if returning true

notice directoryCompilationOptions.extsToCopy is depreacated, if you pass it,directoryCompilationOptions.fileglobsToCopy get invalid.

loaderBox

loaderBox is one new feature started from fib-typify>= 0.3, it depends on new API Sandbox::setModuleCompiler in fibjs>= 0.26.0, but it also work in fibjs >= 0.22.0 < 0.26.0 partly

require typescript directly by default loaderBox

// default-loader.js
const fibTypify = require('fib-typify')

const module = fibTypify.loaderBox.require('./index.ts', __dirname)

require typescript directly by customized loaderBox

// customized-loader.js
const fibTypify = require('fib-typify')

const loaderBox = fibTypify.generateLoaderbox({
    ...fibTypify.defaultCompilerOptions,
    // enable some options as you like
    strict: true,
    diagnostics: true,
    allowJs: true,
})

const module = loaderBox.require('./index.ts', __dirname)

File Filter Priority

High -> Low:

  1. includeLeveledGlobs
  2. fileglobsToCopy
  3. filterFileName

File Writing Priority

  1. [compileResult]
  2. fileglobsToCopy

CLI

Started from 0.2.0, you can run fib-typify in CLI.

fib-typify src -o lib -c .typify.json

Command above means compiling directory src to directory lib with configuration file .typify.json, which would be passed to typescript.transpile(options).

I only provided one simple and crude error exception mechanism, so in some cases it may be not friendly as you like, it's welcome to take PR to help optimizting this part of fib-typify :)

options

-c, --config-file: equals to tsconfig.compilerOptions, would overwrite the one from tsconfig.json

-o, --out-dir: equals to tsconfig.outDir, would overwrite the one from tsconfig.json

Warning

loaderBox Limitations when fibjs < 0.25.0

From fibjs 0.26.0, fibjs supports setModuleCompiler API to customize compiler for specified extension, so we can require typescript file directly by providing compiler for .ts file, which provided by fib-typify's loaderBox.

fib-typify also support loaderBox feature in lower version fibjs(< 0.25.0), but not full-feature support, so there are some advices for your application depending on fib-typify in fibjs(< 0.25.0):

  • always add .ts suffix in require and import statement
  • don't export interface in pure .ts file
  • dont't write loop-requirement with import statement in .ts, if you really do it, write exports.xxx = ... instead of export const xxx = ... in the loop requirement.

so it's better to upgrade fibjs to version>=0.25.0, best to >=0.26.0, which resolves typescript source faster than previous version fibjs in fib-typify.

compile .ts to .js before your deploy

By the way, although I have tested in some cases, but it's not enough to say, "fib-typify's loaderBox can run in production directly". In my own work, I use fib-typify's loaderBox to load all source code when app's in developing stage, but I would compile source to pure javascript code before publishing.

Just use command fib-typify ./src -o ./dist, or use fib-typify's compile* API to build your source code. Get more samples here

TODO

  • There is no official *.d.ts for fibjs yet. I will support generating fibjs.d.ts when compilation. Now Just use fib-types
  • better options for compileDirectoryTo
    • hooks before, when, after compiling
    • on walk to one file recursively
    • customizable recursive
    • support fileglobsToCopy with higher priorty than extsToCopy
  • compile .ts to '.jsc' directly
  • pack compiled '.jsc' to binary and extract one zipped file.
  • --help CLI option for cli

Contributions

If you wanna contribute to this package, just learn about fibjs first, then fork this repo :)

Keywords

FAQs

Package last updated on 25 Nov 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc