Unable to bundle package using Rolldown/Rollup

[trymeouteh]

Rolldown is an new bundler like Rollup but written in Rust which is soon going to be released soon with a stable release and has a Rollup compatible API

https://rolldown.rs/

However I cannot get EJS bundled with my other NPM packages into a UMD bundle. I do know EJS did offer a UMD bundle for browser before. How do I bundle EJS using a bundler today?

[mde]

I'm not sure what you're asking for. There is the same two Browserified files in v4 as there has been in every release:

https://github.com/mde/ejs/releases/download/v4.0.1/ejs.js
https://github.com/mde/ejs/releases/download/v4.0.1/ejs.min.js

Or are you talking about something else?

[mde]

There are also Jake tasks, for doing the build/minify/compress, if you want to do it some other way.

[trymeouteh]

I want to use the NPM package of EJS and place it into a bundle for a web app to use in the browser. No CDNs.

However I am getting errors when using Rolldown when bundling EJS and only EJS, not any of the other packages from NPM I am bundling...

$ npx rolldown ./src/scripts/bundle.js -o ./src/bundle.min.js -f es -n bundle -m
node_modules/ejs/lib/esm/ejs.js (931:2) [COMMONJS_VARIABLE_IN_ESM] Warning: The CommonJS `module` variable is treated as a global variable in an ECMAScript module and may not work as expected
     ╭─[ node_modules/ejs/lib/esm/ejs.js:931:3 ]
     │
 931 │   module.exports = ejs;
     │   ───┬──  
     │      ╰──── 
     │ 
 933 │ export default ejs;
     │ ───┬──  
     │    ╰──── This file is considered to be an ECMAScript module because of the `export` keyword here:
─────╯

node_modules/ejs/lib/esm/ejs.js (21:15) [UNRESOLVED_IMPORT] Warning: Could not resolve 'node:fs' in node_modules/ejs/lib/esm/ejs.js
    ╭─[ node_modules/ejs/lib/esm/ejs.js:21:16 ]
    │
 21 │ import fs from 'node:fs';
    │                ────┬────  
    │                    ╰────── Module not found, treating it as an external dependency
────╯

node_modules/ejs/lib/esm/ejs.js (22:17) [UNRESOLVED_IMPORT] Warning: Could not resolve 'node:path' in node_modules/ejs/lib/esm/ejs.js
    ╭─[ node_modules/ejs/lib/esm/ejs.js:22:18 ]
    │
 22 │ import path from 'node:path';
    │                  ─────┬─────  
    │                       ╰─────── Module not found, treating it as an external dependency
────╯

node_modules/ejs/lib/esm/utils.js (261:2) [COMMONJS_VARIABLE_IN_ESM] Warning: The CommonJS `module` variable is treated as a global variable in an ECMAScript module and may not work as expected
     ╭─[ node_modules/ejs/lib/esm/utils.js:261:3 ]
     │
 261 │   module.exports = utils;
     │   ───┬──  
     │      ╰──── 
     │ 
 263 │ export default utils;
     │ ───┬──  
     │    ╰──── This file is considered to be an ECMAScript module because of the `export` keyword here:
─────╯

Maybe its a Rolldown issue, unless there are additional steps to bundle EJS from the NPM package for browser use?

[mde]

It almost looks like you didn't actually read my response. There are two different files that ship in each release, that are already bundled for use in the browser. There are also Jake tasks that build these files. jake build will run all the build tasks, plus the bundle/minify for the browser, to generate those files.

[trymeouteh]

I tried using jake to build the package and this was the results. Here are my steps to reproduce the jake build stuff.

$ mkdir ejsbundlingtest
$ cd ejsbundlingtest
$ npm init
$ npm i ejs
$ cd node_modules/ejs
$ npm i
$ npx jake build
Starting 'clobberPackage'...
Finished 'clobberPackage' after 0 ms
Starting 'clobber'...
Finished 'clobber' after 0 ms
Starting 'clean'...
Cleaned up compiled files.
Finished 'clean' after 0 ms
Starting 'lint'...

Oops! Something went wrong! :(

ESLint: 9.39.3

Error: ENOENT: no such file or directory, stat '/home/john/Desktop/ejsbundlingtest/node_modules/ejs/eslint.config_esm.mjs'
    at async Object.stat (node:internal/fs/promises:1030:18)
    at async loadConfigFile (/home/john/Desktop/ejsbundlingtest/node_modules/ejs/node_modules/eslint/lib/config/config-loader.js:206:17)
    at async ConfigLoader.calculateConfigArray (/home/john/Desktop/ejsbundlingtest/node_modules/ejs/node_modules/eslint/lib/config/config-loader.js:589:23)
    at async #calculateConfigArray (/home/john/Desktop/ejsbundlingtest/node_modules/ejs/node_modules/eslint/lib/config/config-loader.js:743:23)
    at async entryFilter (/home/john/Desktop/ejsbundlingtest/node_modules/ejs/node_modules/eslint/lib/eslint/eslint-helpers.js:322:5)
    at async NodeHfs.<anonymous> (file:///home/john/Desktop/ejsbundlingtest/node_modules/ejs/node_modules/@humanfs/core/src/hfs.js:574:24)
    at async NodeHfs.walk (file:///home/john/Desktop/ejsbundlingtest/node_modules/ejs/node_modules/@humanfs/core/src/hfs.js:614:3)
    at async globSearch (/home/john/Desktop/ejsbundlingtest/node_modules/ejs/node_modules/eslint/lib/eslint/eslint-helpers.js:364:20)
    at async Promise.allSettled (index 0)
    at async globMultiSearch (/home/john/Desktop/ejsbundlingtest/node_modules/ejs/node_modules/eslint/lib/eslint/eslint-helpers.js:455:18)
jake aborted.
Error: Command failed: node_modules/.bin/eslint --config ./eslint.config_esm.mjs "lib/esm/*.js"
    at genericNodeError (node:internal/errors:998:15)
    at wrappedFn (node:internal/errors:543:14)
    at checkExecSyncError (node:child_process:925:11)
    at execSync (node:child_process:997:15)
    at exec (/home/john/Desktop/ejsbundlingtest/node_modules/ejs/jakefile.js:5:3)
    at Task.action (/home/john/Desktop/ejsbundlingtest/node_modules/ejs/jakefile.js:67:3)
    at Task.run (/home/john/Desktop/ejsbundlingtest/node_modules/ejs/node_modules/jake/lib/task/task.js:329:29)
    at process.processImmediate (node:internal/timers:504:21)

I never had to go inside a package to build it to simply use the package in a bundler, if this is what the jake thing is for.

[mde]

Did you npm install?

[trymeouteh]

Did you npm install?

Yes I npm install ejs and when into the ./node_modules/ejs directory and npm install again before running npx jake build

[mde]

I thought you were cloning the source repo. If you're just installing by NPM, the browserified files are right there in the package.

At the root of the package: ejs.js and ejs.min.js

Those are ready to be used in the browser.