![Maven Central Adds Sigstore Signature Validation](https://cdn.sanity.io/images/cgdhsj6q/production/7da3bc8a946cfb5df15d7fcf49767faedc72b483-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
fib-typify
Advanced tools
just write fibjs with typescript : )
>= 0.26.0
// entry.js
const vm = require('vm')
const typify = require('fib-typify')
typify.loader({
compilerOptions: {
inlineSourceMap: true
}
}).sandbox().require('./index.ts', __dirname)
// index.ts
export function foo (str: string): string {
return `hello, ${str}`
}
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.
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
# locally
fibjs --install fib-typify
# or globally
npm i -g fib-typify
# compile code in ./src to ./dist recursively
fib-typify ./src -o ./dist
{
target: 'es6',
module: 'commonjs',
noImplicitUseStrict: true
}
tsconfig.json
Start from 0.4.0
, compilerOptions
from CWD/tsconfig.json
would overwrite internal default compilerOptions.
function params
tsconfig.json
loader(moduleOptions: any, sourceMapConfig: any, sandBoxCfg?: SandBoxInitialConfig): ChainLoader
generate one ChainLoader
loader().sandbox(mods: object, require: Function, global: object, func?: SetLoaderCallback): Class_SandBox
generate one ChainLoader's sandbox
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
Param | Type | Required/Default |
---|---|---|
baseDir | string | Y / - |
distDir | string | Y / - |
directoryCompilationOptions | directoryCompilationOptions | N / - |
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
Field | Type | Required/Default | Explanation |
---|---|---|---|
compilerOptions | boolean | Y / false | typescript's compilerOptions |
fileglobsToCopy | Array, '*' | N / ['*.js', '*.jsc', '*.json'] | whitelist for extensions of globnames to copy when recursive walk to one |
includeLeveledGlobs | string | string[] | N / ['*', '!node_modules', '!.ts'] |
filterFileName | (filename: string): boolean | N / - | whether compile File, file would be compiled if returning true |
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
// default-loader.js
const Typify = require('fib-typify')
const module = Typify.loaderBox.require('./index.ts', __dirname)
// customized-loader.js
const Typify = require('fib-typify')
const loaderBox = Typify.loader({
compilerOptions: {
...Typify.defaultCompilerOptions,
// enable some options as you like
strict: true,
diagnostics: true,
allowJs: true,
}
}).sandbox()
const module = loaderBox.require('./index.ts', __dirname)
High -> Low:
Started from 0.2.0
, you can run fib-typify
in CLI.
Command above means compiling directory src
to directory lib
with configuration file .typify.json
, which would be passed to typescript.transpileModule(input, moduleOptions)
as 2nd param.
# compile, source directory(such as `src` above) is required
fib-typify src -o lib -c .typify.json
(Started From 0.5.1) run .ts script directly.
fib-typify ./src/index.ts
(Started From 0.5.1) or compile it to same directory with corresponding filename
# get compiled script `./script/index.js`
fib-typify ./src/index.ts -o
(Started From 0.5.1) or compile one file to specified position
# get compiled script `/tmp/a.js`
fib-typify ./src/index.ts -o /tmp/a.js
(Started From 0.5.1) run valid resovable script directly.
## which would try to run `./index.ts`, main script in `package.json`, './index.js', './index.json'...
fib-typify ./
## run `./src/index.js`, `./src/index.ts`, ...
fib-typify ./src
I only provided 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
:)
-c, --config-file
: equals to tsconfig.compilerOptions
, would overwrite the one from tsconfig.json
-o, --out
: (fallback to file when necessary,) equals to tsconfig.outDir
, would overwrite the one from tsconfig.json
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
):
.ts
suffix in require
and import
statement(ESPECIALLY when you run typescript by fib-typify
CLI directly!)export interface
in pure .ts
file.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.
.ts
to .js
before your deployBy the way, although I have tested in some cases, but it's not enough to improve "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
If you wanna contribute to this package, just learn about fibjs first, then fork this repo :)
FAQs
just write fibjs with typescript : )
We found that fib-typify demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
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.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.