Yes better to move in a separate module and compile it at build time. It is actually a component we developed but is not yet used by the tasks.
Michele Sciabarra | CTO m: +44 747 984 8388 e: [email protected] l: https://linkedin.com/in/msciab Nuvolaris Inc | 1209 Orange Street, 19801Wilmington DE - US Michele Sciabarra | CTO m: +44 747 984 8388 e: [email protected] l: https://linkedin.com/in/msciab Nuvolaris Inc | 1209 Orange Street, 19801Wilmington DE - US On Mon, 28 Sept 2026 at 09:15, Jean-Baptiste Onofré <[email protected]> wrote: > > Hi Xuanwo, > > As far as I recall, this was discussed during a previous release candidate. > Instead of bundling the entire configurator directory, I would prefer to > update the build documentation instead. > > Regards, > JB > > > On Mon, Sep 28, 2026 at 8:31 AM Xuanwo <[email protected]> wrote: >> >> -1 (binding) >> >> I verified the checksum, GPG signature, source correspondence, >> license headers, and CLI build and unit tests. >> >> However, the source archive includes >> oplugins/util/config/configurator.js but excludes the entire >> oplugins/util/config/configurator directory through no-release.txt. >> >> That directory contains the TypeScript sources, package.json, >> lockfile and tests needed by the documented build procedure. >> The shipped component therefore cannot be rebuilt from the >> source release as provided. >> >> Please include those source and build inputs in the source >> distribution and prepare a new release candidate. >> >> Thanks, >> Xuanwo >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
