f0f4bcb24Update Batch.md15a8b1de6Update Batch.mdeb841ce66Update theme751097f24Use CI_PAGES_URL in GitLab Pages workflow8584a0581Fix typosb030a7149Update configuration.mdf7ec2ee9cRevert "Update shortcode.md"f8188f1c8Update shortcode.md083fc39c6Update shortcode.mdd4bdfb96bUpdate Filter.mdef00649dbDocument wrapperClass highlighting optione227dc422Hugo 0.140.2b95d28444Fix description of the the hugo server command41ca381b0Fix documentation of Fragments73a6cd966Update theme2573fd120netlify: Hugo 0.140.190b19ec0dMerge branch 'tempv0.140.1'ad2e9aeecUpdate gocloud and docs for S3-Compatible Endpoints34b30bad2Remove indentation from include shortcode examples97b4ef544Update related.md7234e0189Update related.md32cc191f6Clarify Name and Title menu entry methodsbce733c63Update theme2f1843d10Use .Page.GetPage in examples of an include shortcode9e1c85bbdRevert "Document PAGE.String"bb30e7c08Document PAGE.String2d151d77fFix linkfbe2d442fMiscellaneous updates for v0.140.04d3195223Update JS docs vs Hugo v0.1408c190aabcnetlify: Hugo 0.140.0826005ffeMerge branch 'tempv0.140.0'107289a2cUpdate theme (again)9884425f9Update themeff0a358d3Update Go tool version in hugo.workc9b23cf6dtpl/tplimpl: Update details shortcodef29f19afftpl/tplimpl: Add details shortcode git-subtree-dir: docs git-subtree-split:f0f4bcb243
4.6 KiB
title, description, weight, categories, keywords, action, toc
| title | description | weight | categories | keywords | action | toc | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| js.Build | Bundles, transpiles, tree shakes, and minifies JavaScript resources. | 30 |
|
true |
The js.Build function uses the evanw/esbuild package to:
- Bundle
- Transpile (TypeScript and JSX)
- Tree shake
- Minify
- Create source maps
{{ with resources.Get "js/main.js" }}
{{ if hugo.IsDevelopment }}
{{ with . | js.Build }}
<script src="{{ .RelPermalink }}"></script>
{{ end }}
{{ else }}
{{ $opts := dict "minify" true }}
{{ with . | js.Build $opts | fingerprint }}
<script src="{{ .RelPermalink }}" integrity="{{ .Data.Integrity }}" crossorigin="anonymous"></script>
{{ end }}
{{ end }}
{{ end }}
Options
- targetPath
- (
string) If not set, the source path will be used as the base target path. Note that the target path's extension may change if the target MIME type is different, e.g. when the source is TypeScript. - format
- (
string) The output format. One of:iife,cjs,esm. Default isiife, a self-executing function, suitable for inclusion as a<script>tag.
{{% include "./_common/options.md" %}}
Import JS code from /assets
js.Build has full support for the virtual union file system in Hugo Modules. You can see some simple examples in this test project, but in short this means that you can do this:
import { hello } from 'my/module';
And it will resolve to the top-most index.{js,ts,tsx,jsx} inside assets/my/module in the layered file system.
import { hello3 } from 'my/module/hello3';
Will resolve to hello3.{js,ts,tsx,jsx} inside assets/my/module.
Any imports starting with . is resolved relative to the current file:
import { hello4 } from './lib';
For other files (e.g. JSON, CSS) you need to use the relative path including any extension, e.g:
import * as data from 'my/module/data.json';
Any imports in a file outside /assets or that does not resolve to a component inside /assets will be resolved by ESBuild with the project directory as the resolve directory (used as the starting point when looking for node_modules etc.). Also see hugo mod npm pack. If you have any imported npm dependencies in your project, you need to make sure to run npm install before you run hugo.
Also note the new params option that can be passed from template to your JS files, e.g.:
{{ $js := resources.Get "js/main.js" | js.Build (dict "params" (dict "api" "https://example.org/api")) }}
And then in your JS file:
import * as params from '@params';
Hugo will, by default, generate a assets/jsconfig.json file that maps the imports. This is useful for navigation/intellisense help inside code editors, but if you don't need/want it, you can turn it off.
Node.js dependencies
Use the js.Build function to include Node.js dependencies.
Any imports in a file outside /assets or that does not resolve to a component inside /assets will be resolved by esbuild with the project directory as the resolve directory (used as the starting point when looking for node_modules etc.). Also see hugo mod npm pack. If you have any imported npm dependencies in your project, you need to make sure to run npm install before you run hugo.
The start directory for resolving npm packages (aka. packages that live inside a node_modules folder) is always the main project folder.
{{% note %}}
If you're developing a theme/component that is supposed to be imported and depends on dependencies inside package.json, we recommend reading about hugo mod npm pack, a tool to consolidate all the npm dependencies in a project.
{{% /note %}}
Examples
{{ $built := resources.Get "js/index.js" | js.Build "main.js" }}
Or with options:
{{ $externals := slice "react" "react-dom" }}
{{ $defines := dict "process.env.NODE_ENV" `"development"` }}
{{ $opts := dict "targetPath" "main.js" "externals" $externals "defines" $defines }}
{{ $built := resources.Get "scripts/main.js" | js.Build $opts }}
<script src="{{ $built.RelPermalink }}" defer></script>