regl-web-components 0.0.1

package/.nvmrc

@@ -0,0 +1 @@
+22.13.0

package/.rr.todo.md

@@ -0,0 +1,15 @@
+- regl-intersecting-web-component
+  - a regl component that initializes on intersection observer, and destroys after. maybe we could use deferred regl for this, setting the regl instance when its approaching the viewport
+    - curious if this is more performant than mult-regl?
+- regl-multi-web-component
+  - make mult-regl based on web components
+  - avoid using getBoundingClientRect, can we just use the subcontext intersection observer response to do the offsets to determine the viewport
+
+
+- renamed variables to be more consistent
+
+todo
+
+× shadow dom for the canvas element? probs not necessary
+× start work on multi-regl
+× debug why my regl-multi-element doesnt render anything

package/bundler/esbuild.build.mjs

@@ -0,0 +1,7 @@
+import { build } from 'esbuild'
+import config from './esbuild.config.mjs'
+
+await build({
+  ...config,
+  outdir: 'dist',
+})

package/bundler/esbuild.config.mjs

@@ -0,0 +1,22 @@
+import aliasPlugin from 'esbuild-plugin-path-alias'
+
+export default {
+  entryPoints: [
+    'src/all.ts',
+    'src/all-define.ts',
+    'src/regl-element.ts',
+    'src/regl-element-define.ts',
+    'src/regl-multi-element.ts',
+    'src/regl-multi-element-define.ts',
+    'src/regl-multi-root.ts',
+    'src/regl-multi-root-define.ts',
+  ],
+  outdir: 'example',
+  bundle: true,
+  format: 'esm',
+  plugins: [
+    aliasPlugin({
+      '@': process.cwd(),
+    }),
+  ],
+}

package/bundler/esbuild.watch.mjs

@@ -0,0 +1,14 @@
+import * as esbuild from 'esbuild'
+import config from './esbuild.config.mjs'
+import {join} from 'node:path'
+
+let ctx = await esbuild.context({
+  ...config,
+})
+
+await ctx.watch()
+
+let { host, port } = await ctx.serve({
+  servedir: join(process.cwd(), 'example'),
+})
+console.log(`Watching: ${host}:${port}`)