Installations
npm install tauque
Developer Guide
Typescript
No
Module System
ESM
Node Version
16.5.0
NPM Version
7.19.1
Score
71.1
Supply Chain
97.6
Quality
76.2
Maintenance
100
Vulnerability
99.6
License
Releases
Contributors
Unable to fetch Contributors
Languages
JavaScript (100%)
Developer
CTNicholas
Download Statistics
Total Downloads
4,540
Last Day
3
Last Week
42
Last Month
113
Last Year
528
GitHub Statistics
16 Stars
51 Commits
1 Forks
2 Watching
1 Branches
1 Contributors
Package Meta Information
Latest Version
1.5.1
Package Id
tauque@1.5.1
Unpacked Size
301.24 kB
Size
248.38 kB
File Count
48
NPM Version
7.19.1
Node Version
16.5.0
Total Downloads
Cumulative downloads
Total Downloads
4,540
Last day
0%
3
Compared to previous day
Last week
31.3%
42
Compared to previous week
Last month
189.7%
113
Compared to previous month
Last year
-24.4%
528
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
4
Tauque (pronounced /tɔːk/, like torque) is a zero-configuration JS/TS bundler with serious pulling power. It uses esbuild under the cover, meaning it transpiles up to 100x quicker than Rollup/Webpack with Babel.
Install:
1npx install-tauque
Create a dist
folder with bundles (no-config needed):
1npm run dev
Tauque can bundle
- JavaScript (with optional transpilation)
- TypeScript
- JSX
- CSS (files and js imports)
- JSON
Dev mode watching for file changes and running cumulative builds, most taking around 10ms:
Install
Install Tauque on a project that's already set up, and it'll take your entry point from package.json
(or try to find it elsewhere)
and automatically create a config file that's ready to run.
1npx install-tauque
Ready to go!
Tauque is now ready to run. Bundles will be written to the dist
folder by default. Run tauque dev mode with:
1npm run dev
A single time build can also be run with:
1npm run build
Alternative install
You can also Tauque without building config and readme files:
1npm install tauque
Config options
A tauque.json
config file will automatically be generated when you first install Tauque.
This should be placed alongside package.json
in your project root.
All config options, with default settings:
1// Name of the final file (required) 2"name": "packageName" 3 4// Location of the entry point (required) 5"source": "src/index.js", 6 7// Package type: "module" (also "esm"); "browser" (also "iife"); "node" (also "cjs"); "all" 8"type": "all", 9 10// Global variable name of export in browser/iife packages 11"global": "packageName", 12 13// Directory for output package 14"outputDir": "dist", 15 16// Directory to watch for changes 17"watchDir": "src", 18 19// Target environment, eg: ["es2020", "chrome58", "firefox57", "node12.19.1"] 20"target": ["es6"], 21 22// Bundle imports: true, false 23"bundle": true, 24 25// Minify package: true, false 26"minify": true, 27 28// Generate separate source map file 29"sourceMap": true, 30 31// Automatically add environment variables 32"useEnvVariables": true, 33 34// Native esbuild settings to pass on (overrides Tauque) 35"esbuild": {}
Note that comments are not allowed in JSON files.
Config examples
A list of tauque.json
config examples with the dist
folders they create.
All unset options inherit the default settings shown above.
Single output config
1{ 2 "name": "my-package", 3 "source": "src/index.js" 4}
- dist/
¬ my-package.browser.js
¬ my-package.browser.js.map
¬ my-package.module.js
¬ my-package.module.js.map
¬ my-package.node.js
¬ my-package.node.js.map
Multiple output config
1[ 2 { 3 "name": "my-iife-package", 4 "source": "src/index.js", 5 "type": "browser" 6 }, 7 { 8 "name": "my-esm-package", 9 "source": "src/index.js", 10 "type": "module" 11 } 12]
- dist/
¬ my-iife-package.js
¬ my-iife-package.js.map
¬ my-esm-package.js
¬ my-esm-package.js.map
Multiple input/output config
1[ 2 { 3 "name": "my-client", 4 "source": "src/client.js", 5 "outputDir": "dist/client", 6 "type": "browser" 7 }, 8 { 9 "name": "my-server", 10 "source": "src/server.js", 11 "outputDir": "dist/server", 12 "type": "node" 13 } 14]
- dist/
- client/
¬ my-client.js
¬ my-client.js.map
- server/
¬ my-server.js
¬ my-server.js.map
Complex config
1[ 2 { 3 "name": "client", 4 "source": "src/client/index.js", 5 "outputDir": "build-client", 6 "type": "browser", 7 "sourcemap": false, 8 "minify": false, 9 "esbuild": { 10 "banner": "/* Package made by CTNicholas */", 11 "define": { 12 "mode": "debug" 13 } 14 } 15 }, 16 { 17 "name": "client.min", 18 "source": "src/client/index.js", 19 "outputDir": "build-client", 20 "type": "browser" 21 }, 22 { 23 "name": "server", 24 "source": "src/server.js", 25 "outputDir": "build-server", 26 "type": "node", 27 "sourcemap": false, 28 "minify": false, 29 "bundle": false 30 } 31]
- build-client/
¬ client.js
¬ client.min.js
¬ client.min.js.map
- build-server/
¬ server.js
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE.md:0
- Info: FSF or OSI recognized license: MIT License: LICENSE.md:0
Reason
0 existing vulnerabilities detected
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Score
3
/10
Last Scanned on 2025-01-27
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More