Javascript Modules Engine

This release adds support for Vite-powered asset bundling.

Breaking Changes

• The Vite plugin no longer inlines all resources! This is an important change for both performance and security. (#275)

  What it means in practice is that instead of two output folders (client and server), there are now three output folders:

  • server: contains a single JS file to run on the server
  • client: contains all JS files used for hydration
  • assets: contains a single CSS file (style.css), with resources referenced in CSS and JS files (fonts, images...)

  Assets will be deduplicated between client and server builds.

  The configuration structure of the plugin changed to reflect this new folder. Here is the new default configuration:

  jahia({
    inputDir: "src",
    outputDir: "dist",
    assetsDir: "assets", // Computed as dist/assets
    client: {
      inputGlob: "**/*.client.{jsx,tsx}", // Computed as src/**/*.client.{jsx,tsx}
      outputDir: "client", // Computed as dist/client
    },
    server: {
      inputGlob: "**/*.server.{jsx.tsx}", // Computed as src/**/*.server.{jsx,tsx}
      outputFile: "server/index.js", // Computed as dist/server/index.js
    },
  })

   

• If you follow our conventions regarding file names (see the globs above), you can safely remove all pre-0.8 configuration settings.

  You will need to update your CSS import: <AddResources type="css" resources={buildModuleFileUrl("dist/assets/style.css")} /> (assets instead of server)

  You may now restrict web-accessible resources in your package.json: "static-resources": "/dist/client,/dist/assets"

• The jahia-deploy CLI has been rewritten to improve the development experience: CND breaking change validation is now skipped during development, allowing easier prototyping. The new CLI always uses the provisioning API. (#378)

• Hydration markers now use custom elements instead of <div>s to prevent invalid HTML. All custom elements are prefixed by jsm- to avoid collisions. The new elements used are jsm-hydrate, jsm-render and jsm-children. (#386)

New Features

• The npm create @jahia/module@latest CLI has been revamped to offer different templates to start your integration with. (#407)

  You can now choose between 3 different bases:

  • A minimal Hello World template set (this was the only available base previously)
  • An empty template set
  • An empty module

  Newly created modules now ship with a docker-compose.yml file to ease the creation process of a local Jahia instance. (#364)

• RenderChild and RenderChildren now accept a nodeTypes prop, used in page builder to restrict the node types that can be added as children. (#379)

• Vite 7 is now officially supported! (#387)

• buildModuleFileUrl keeps base64 URLs untouched instead of crashing. This features pairs well with Vite's assets handling. (#394)

Embedded JS Packages

No breaking changes here, we bumped JSM dependencies to the following versions:

• react: 19.1.0
• i18next: 25.3.2
• react-i18next: 15.6.0

Full Changelog: 0_7_2...0_8_0

No changes from 0.7.1

This release adds support for JS<->Java interactions through OSGi services.

New Features

• JS code can interact with Java code through OSGi services. Usage looks roughly like this:

  import { jahiaComponent, server } from "@jahia/javascript-modules-library";
  
  jahiaComponent(
    {
      nodeType: "javascriptExample:testOSGi",
      name: "default",
      componentType: "view",
    },
    () => <p>{server.osgi.getService("org.example.services.SimpleService").sayHello("World")}</p>,
  );

   

• The documentation will be updated shortly with more details on how to use this feature. In the meantime, you can check #294 for more examples. If you have feedback on this feature, please reach out to us: calendar.app.google/LigWTiUSDeHmVCwa7

• JS client files are now minified. This should save up to 1 MB of client-side JavaScript for cold page loads! #269

• process.env.NODE_ENV is now replaced during the build. This change makes JavaScript Modules more compatible with the rest of the Node.js ecosystem. #263

• Sourcemaps are generated by default in development mode. #272

Breaking Changes

• buildNavMenu has been removed. #282

Dependency Updates (#299)

All runtime dependencies have been updated to the latest versions. This includes:

• i18next: 23.10.1 → 25.0.2 (🚨 Check i18next.com/misc/migration-guide for breaking changes affecting you)
• react: 19.0.0 → 19.1.0
• react-i18next: 15.4.0 → 15.5.1
• styled-jsx: 5.1.6 → 5.1.7

Other Changes

• All packages of this monorepo are now published to maven/npmjs.com on every commit. You can check the versions tab to install pre-release versions. Be careful, pre-releases do not go through our QA step. #254 and #281
• You should no longer experience issues with jExperience and page-level personalization. #295
• GraalVM is now correctly detected. #293

Full Changelog: 0_6_1...0_7_0

JavaScript Modules are not compatible with Jahia 8.2.0.x.

This releases enforces that by raising the minimum Jahia version to 8.2.1.0.

This release contains a lot of breaking changes since the last published version of JavaScript Modules Engine:

• Version 0.5 breaking changes
• Version 0.6 breaking changes

(Note: 0.4 does not have exposed breaking changes)

• Rename from "NPM Modules" => "JavaScript Modules"
• Introduce dependency to javascript-modules-engine in all JS modules
• New helpers to build URLs
• Easier way to generate URLs for resources in static folder
• Simplification of folder structure 
• Production build config for npm-module-engines and JS modules
• Update version or Yarn (no pnp)
• Remove dependencies of libraries that are provided by Jahia at runtime: react, i18next, react-i18next, prop-types
• Merge npm-modules-engine and js-server-core in one open source Github repo: https://github.com/Jahia/javascript-modules