<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Old version of rollup]]></title><description><![CDATA[<p dir="auto">Why does JSCAD use the very old version of rollup? By runing</p>
<pre><code class="language-bash">for pf in `find -name 'package.json' | grep -v node_modules`; do echo $pf; grep 'rollup' $pf ; done
</code></pre>
<p dir="auto">I get the version 2.79.1. I don't have problem with old version of a software, as long as it works and I can find the document of the old version.</p>
<p dir="auto">Let me explain the background why I need to use rollup.<br />
I want to extend the document with embedded running examples. So I make a small static JS-file to use it in each JSDoc generated HTML-files to display example. This static JS file should import the same JS modules in the repository, show I can automatically keep it consistent with versions of JSCAD:</p>
<pre><code class="language-javascript">// filename web-render.es.js
import { cameras, commands, controls, entitiesFromSolids, prepareRender } from "@jscad/regl-renderer"

export const render = (shapes, domId) =&gt; {
// .... Do something here
}
</code></pre>
<p dir="auto">This file is then converted into <code>web-render.js</code>, which exposes the fuction <code>render</code> into global scope, and can be easily used as</p>
<pre><code class="language-html">&lt;script src="web-render"&gt;&lt;/script&gt;
&lt;!--  some where in the doc: --&gt;
&lt;div id="sphere-demo"&gt;&lt;/div&gt;
&lt;script&gt;
render(model, "sphere-demo")
&lt;/script&gt;
</code></pre>
<p dir="auto">My questions:</p>
<ul>
<li>Why JSCAD does use the old version of rollup?</li>
<li>Where can I find the old document of the used rollup version?</li>
<li>If the document does not exist anymore, how much effort does it take to port the old version to the new of rollup?</li>
</ul>
]]></description><link>https://openjscad.nodebb.com/topic/439/old-version-of-rollup</link><generator>RSS for Node</generator><lastBuildDate>Wed, 16 Sep 2026 04:04:20 GMT</lastBuildDate><atom:link href="https://openjscad.nodebb.com/topic/439.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 22 Feb 2025 22:21:28 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Old version of rollup on Sun, 23 Feb 2025 22:09:27 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/hpb-htw" aria-label="Profile: hpb-htw">@<bdi>hpb-htw</bdi></a> Super! You understand well.</p>
<p dir="auto">Each package will have a slightly different version, as Lerna determines major/minor/fix versions by changes. The main package is never released so, the version stays the same, but should be 3.0.0.</p>
<p dir="auto">Please take another look at utils/regl-renderer package. The demo html files are slightly different in V3.</p>
]]></description><link>https://openjscad.nodebb.com/post/1466</link><guid isPermaLink="true">https://openjscad.nodebb.com/post/1466</guid><dc:creator><![CDATA[z3dev]]></dc:creator><pubDate>Sun, 23 Feb 2025 22:09:27 GMT</pubDate></item><item><title><![CDATA[Reply to Old version of rollup on Sun, 23 Feb 2025 19:39:09 GMT]]></title><description><![CDATA[<p dir="auto">How about version policy? I see that in the branch V3 the main <code>package.json</code> has the version <code>2.0.0</code>, some other packages have version <code>3.0.1-alpha.0</code>. So if I correctly understand: each package should have a version of itself, shouldn't it?</p>
]]></description><link>https://openjscad.nodebb.com/post/1465</link><guid isPermaLink="true">https://openjscad.nodebb.com/post/1465</guid><dc:creator><![CDATA[hpb-htw]]></dc:creator><pubDate>Sun, 23 Feb 2025 19:39:09 GMT</pubDate></item><item><title><![CDATA[Reply to Old version of rollup on Sat, 22 Feb 2025 23:33:53 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/hpb-htw" aria-label="Profile: hpb-htw">@<bdi>hpb-htw</bdi></a> V2 uses Lerna to manage each package, including building and publishing the distributions to NPM. See the link in the main README.</p>
<p dir="auto">As part of the build process. Lerna calls the build step of each package. This step uses browserify.</p>
<p dir="auto">If you switch to the V3 branch then you will find that The build step is using rollup.</p>
<p dir="auto">So, be careful. Don't mix the versions.</p>
<p dir="auto">By the way, the CONTRIBUTING document explains how to setup, make changes, test changes, and submit changes back to GIT. Please follow the document.</p>
]]></description><link>https://openjscad.nodebb.com/post/1463</link><guid isPermaLink="true">https://openjscad.nodebb.com/post/1463</guid><dc:creator><![CDATA[z3dev]]></dc:creator><pubDate>Sat, 22 Feb 2025 23:33:53 GMT</pubDate></item></channel></rss>