@griddo/vundle

Griddo vite bundler configuration for Griddo Instance projects.

Cambios en la isntancia

mover

📦 Installation

npm install @hiscovega/vundle # at @hiscovega org for the beta testing

🚀 Usage

Build (from a client project)

Run Vite using this package config:

vite build --config node_modules/@hiscovega/vundle/vite.config.mjs

The bundler will look for the client vite.config.* in the current working directory and merge it on top of the master config.

Client Configuration (vite.config.mjs)

Create a vite.config.mjs (or .ts/.js) in your project root to customize the build configuration.

// vite.config.mjs (in your project root)
export default {
  plugins: [
    // Additional Vite plugins for your project
  ],

  // Standard Vite/Rollup external (advanced). It will be COMPOSED with the bundler externals.
  // build: { rollupOptions: { external: (id) => id === "my-heavy-dep" } },

  griddoOptions: {
    customExternals: [
      "some-heavy-package-foo", // Mark as external by exact name
      // /^@company\//, // Mark all packages from a scope as external
    ],
  }
};

Notes

• Mandatory externals: React, React DOM and @griddo/core are always externalized by the bundler.
• Optional assets: static/ and thumbnails/ are copied into dist/ if they exist. If they don't exist, the build will not fail.

Bundle output

The bundle exports four artifacts:

dist/index.js # Legacy instance entry: templates, modules, components, contexts, etc.
dist/builder.js # Builder-related files (legacy): builder.browser.jsx, builder.ssr.jsx and builder.config.js
dist/griddo.config.js # Legacy griddo.config.ts
dist/builder.css # All instance CSS bundled

Importing in AX / CX:
import { SiteProvider, bundle, components, formsTemplates, templates } from "<bundle>"
import { browser, config, ssr } from "<bundle>/builder"
import griddoConfig from "<bundle>/griddo.config"
import "<bundle>/builder.css"

✅ Testing

npm test

🧪 Local fixture (simple client)

This repo includes a minimal client fixture under fixtures/client/:

npm run fixture:build

🚀 Publishing

This package uses release-it for automated versioning and publishing.

Tip: if you run releases in a non-interactive environment (no TTY), use:

npm run release:patch -- --ci