NV Elements Catalog Starters Repo System Themes About Getting Started Changelog Metrics Support Accessibility Contributions Requests Migration Deprecations Integrations Installation MCP CLI Lint Angular Bundles Extensions Go Hugo Import Maps Lit NextJS Nuxt Preact React SolidJS Svelte TypeScript Vue Foundations Typography Iconography Themes Design Tokens Size & Space Objects Interactions Support Status Color Animation Fonts Layers Custom Layout Horizontal Vertical Grid Popovers i18n Visualization View Transitions Elements Accordion Alert Avatar Badge Breadcrumb Button Button Group Card Chat Message Checkbox Color Combobox Copy Button Datagrid Integrations Column Action Column Alignment Column Fixed Column width Container Card Display Settings Footer Heatmap Keynav Multi Select Pagination Panel Detail Panel Grid Performance Placeholder Row Action Row Groups Row Sort Scroll Height Single Select Stripe Date Datetime Dialog Divider Dot Drawer Dropdown Dropdown Group Dropzone File Forms Validation Actions Control Icon Icon Button Input Input Group Logo Menu Month Notification Page Page Header Page Loader Pagination Panel Progressive Filter Chip Progress Bar Progress Ring Password Preferences Input Pulse Radio Range Resize Handle Search Select Skeleton Sort Button Sparkline Star Rating Steps Switch Tabs Tag Textarea Time Toast Toggletip Toolbar Tooltip Tree Week Patterns Authentication Browse Dashboard Editor Empty States Heatmap Keyboard Shortcut Logging Media Onboarding Panel Responsive Search Subheader Trend Code Codeblock Monaco Input Diff Input Editor Diff Editor Problems Markdown Markdown CSS Utility Labs Responsive Layout Viewport Container Patterns Forms API Design Properties & Attributes Slots Registration CustomEvents Stateless Composition Styles Packaging Glossary Logs Internal Guidelines Agent Harness Documentation Examples TypeScript Testing Unit Testing Accessibility Testing Lighthouse Testing SSR Testing Visual Testing Troubleshooting Component Creation Internal Examples All Examples

Go

Download Source Documentation

Install CLI

Install the Elements CLI to your system. This will add the nve command to your path and provide several helpful commands for working with Elements.

MacOS / Linux Windows CMD NodeJS

Create a New Project

Use the Elements CLI to quickly bootstrap a new go project with the necessary dependencies:

Setup an Existing Project

Setup an existing project to use Elements you can use the setup command to add the necessary dependencies and configure the MCP server.

If not yet done, install NodeJS. NodeJS is a JavaScript runtime that has a large ecosystem of tooling and packages for Web Development. Once installed the Node Package Manager (NPM) will be available for use.

Manual Integration

If installing to an existing project, install the core dependencies:

Elements is agnostic to any frontend or backend tooling. To leverage elements in Go based templating two paths are available.

  1. Static bundles with little to no JavScript ecosystem tooling
  2. Build time tooling with NodeJS and npm packages

The current simple Go starter provides an example of a basic Go web server leveraging the pre-built JS and CSS bundles. This enables Go generated HTML pages with minimal NodeJS/JavaScript ecosystem tooling.

But, if you would like to integrate advanced tooling such as TypeScript, treeshaking or other JavaScript ecosystem tools and packages consider leveraging tools like Vite and Vite Go

Registry Usage Guidelines

Enterprise environments requiring strong security posture and legal compliance, using a package manager and Artifactory is strongly recommended.

Security and Licensing Risks

When choosing between static bundles and build-time tooling with a package manager, it's important to consider security and legal compliance:

  • Automated Vulnerability Scanning: NPM/PNPM and Artifactory provide built-in security scanning that detects known vulnerabilities in dependencies
  • Dependency Auditing: Package managers track the complete dependency tree, making it easy to audit third-party libraries and identify versions used
  • License Compliance: Automated license scanning helps compliance with legal requirements by flagging incompatible/restricted licenses
  • Update Management: Centralized package management enables coordinated security updates, ensuring critical patches are applied consistently
  • Version Control: Package lock files provide reproducible builds while keeping the actual library code out of source control

Committing Third-Party Libraries to Source Control Risks

  • License Violations: Manual license tracking is error-prone and may result in using libraries with incompatible or restricted licenses, creating legal liability
  • Hidden Vulnerabilities: Without automated scanning, security vulnerabilities in committed libraries may go undetected until they're exploited
  • Stale Dependencies: Committed libraries are often not updated regularly, leaving projects exposed to known security issues
  • Audit Complexity: Determining which third-party code is present, what versions are in use, and their license terms becomes a manual, time-consuming process
  • Repository Bloat: Large binary files and library code increase repository size and slow down clone operations