Migrate to ES Module structure/runtime - Node 20, Vite, Vitest, Storybook 8 #272

twelch · 2024-03-07T01:08:27Z

Dev

Key Requirements/Decisions

Switch from Jest to Vitest, supports ESM out of the box and is mostly Jest compatible API
Switch from webpack to esbuild, supports ESM out of the box and more easily configurable.
Switch from ts-node to tsx. Better node 20 and esm support out of the box.
upgrade flatgeobuf, and upgrade the docker-gp-workspace to the latest GDAL
request fix to geoblaze to work in ESM environment, v2.6.1 - https://github.com/GeoTIFF/geoblaze/commits/master/

ToDo

Testing

Add flatgeobuf.ts test using local file
Verify devcontainer is working with unstable release of docker-gp-workspace

Release

Init a new project from scratch and go through to deploy - create sketch and collection, import data, test, deploy, publish data.
Migrate an existing gp project
Write migration doc
- Add "type": "module" to package.json
- Update tsconfig.json
- Restart vscode for it to start recognizing use of esm mode
- update package.json scripts, dependences, devDependencies. Can copy and overwrite directly from [insert link to release
- install:scripts, then translation:install to upgrade
  file] and add back any that you added just for the project, if any.
Update docs
- ANALYZE and MINIFY vars for build command
- Note use of nvm alias default v20.12.1 and nvm use default in vscode terminal if your vscode terminal keeps not using the right version of node
- devcontainer upgrade, to get access to node20, latest GDAL, etc.
- writeup how CLI commands work. They run in gp space using gp dependencies, but run against the project space. Build commands additionally bundle the report and gp/pp functions first in project space?
- Use of unstable devcontainer and how to pull the latest docker pull seasketch/geoprocessing-workspace:unstable
- named export required for report component in order for example-reports to work
- Document static asset handling, and importing images - https://vitejs.dev/guide/assets.html#static-asset-handling

Follow-on tickets:

Basic smoke test fails for ecoregions, FAIL src/functions/simpleFunctionSmoke.test.ts > Basic smoke tests > simpleFunction
- tests run against all examples
- FetchError: request to https://gp-global-datasources-datasets.s3.us-west-1.amazonaws.com/meow-ecos.fgb failed, reason: socket hang up
- error happens with FSM region, but not Azores, something with the data there? Or does it result in many or very large polygons?
fix snapshot update via test:scripts:update, need to migrate away from jest-based solution
Do sideEffects need to be added back for fetchPolyfill?
Vitest - leftovers from Switch from Jest to Vitest #273
- Migrate to new aws-cdk/assertion library, assert lib has reached EOL, and also how we use it relies on Jest.
- GeoprocessingHandler.test.ts has old jest mock
- Setup vitest with at_testing-library/jest-dom -https://github.com/testing-library/jest-dom?tab=readme-ov-file#installation via Export Vitest extend-expect testing-library/jest-dom#439 (comment)
- browser tests (fix mocking)
- e2e tests (fix mocking)
- Fix all skipped tests
- Fix vitest globals so explicit import not needed
- Switch to Vitest workspace - https://vitest.dev/guide/workspace.html
Once migrate to aws-sdk v3, bring back the dynamodb tests - https://daaru.medium.com/testing-lambda-functions-with-vitest-fc713caa975d
Once migrate to aws-sdk v3, filter it and aws-cdk out of the function builds using externals
upgrade Typescript and switch from assert type JSON to with
Update base translations
Merge client-ui and client-core
Reduce project dependencies by bringing CLI commands into GP space (via cd GP_PATH) so that GP dependencies are used. translation:extract is one example where babel and plugin should be able to be moved.
Try to use top-level turf library
Consolidate src and scripts into one tsc build step (assuming pure esm)
Enable eslint - with warnings
Add monorepolint like turf uses for template packages
Convert "G extends Geometry" to "G extends Geometry | null" to support null geometry case?
Update React
Update i18next
Migrate from polygon-clipping back to turf clip if possible
v7 release:
Publish new base EN translations and translate them to all languages

Old - will not do

Webpack
- Migrate client-loader.js to esm export, and to generate ESM report loader code
- Migrate webpack.client.config.js to ESM - see https://github.com/firebase007/webpack-demo/blob/master/webpack.config.js and article https://blog.logrocket.com/transpile-es-modules-with-webpack-node-js/.
- Migrate webpack.functions.config.js to ESM
- Upgrade to webpack 5 and stop the use of NODE_OPTIONS=--openssl-legacy-provider
- Convert App.tsx require to dynamic import, see (https://stackoverflow.com/questions/50976936/how-to-get-dynamic-imports-to-work-in-webpack-4)
- https://stackoverflow.com/questions/64796952/webpack-ts-loader-import-with-js-extension-not-resolving
- https://stackoverflow.com/questions/51356071/how-to-pass-parameters-from-web-pack-to-code

Questions

What does the top-level tsconfig.json do? Should it be updated or deleted?
- Doesn't seem to be used so deleted it. See if it breaks anything.
Should I use "module": "node16" like sindresorhus suggests instead of "module": "nodenext" like Typescript suggests?
- Switched to nodenext, to get json assert support, which new project init was throwing an error on for import of all json files, even though node16. 🤷
- node16 should work best with everything in toolchain, and it will be stable/fixed. nodenext can/will change when Typescript is upgraded.
Is "target": "es2022" for both src and scripts correct?
- Yes, assuming webpack can handle it at the project build stage. This should ensure that the most modern esm code is generated by the typescript transpiler.
Should I have esModuleInterop and allowSyntheticDefaultImports enabled?
- Let's leave them enabled if they already are for now.
What to replace require.resolve with in CJS files?
- require.resolve returns a file path to a code files. There is an esm equivalent - https://stackoverflow.com/questions/54977743/do-require-resolve-for-es-modules
- https://dev.to/stephencweiss/what-is-require-resolve-and-how-does-it-work-1ho4
- area.test.ts turf area output changed by about .25%. Why?
  - @turf/area Fix earth radius to use WGS84 median earth radius (#2166)

Notes on steps

nvm install 20.11.1
npx lern init
Add packages/geoprocessing
Copy old package.json and modify for esm and type import
- Add type: "module" tell node that .ts and .js files are ESM.
- Add type import to exports - https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-7.html
Copy over and update tsconfig.json
- https://github.com/tsconfig/bases/blob/main/bases/node20.json
- node16 moduleResolution provides support for ES Modules
Update Typescript
- You must use a .js extension in relative imports even though you're importing .ts files.
ts-node fails with node v20 to run .ts files
- TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for ...
- ERR_UNKNOWN_FILE_EXTENSION on Node v20.0.0 TypeStrong/ts-node#1997
- Switch to using tsx, works out of box
Jest - not working properly, cant find tests...
- Possibly has to do with .js file extension - ES import of typescript with .js extension fails swc-project/jest#64
- Trying out vitest as alternative
- https://blog.hao.dev/setting-up-vitest-within-sveltekit-repo
- https://vitest.dev/guide/#configuring-vitest
- Testing out using Node test runner for geoblaze tests which works. Potential to run node tests separately, see How to run the Node built-in testrunner for TypeScript files inside a specific directory? nodejs/help#3902, and using glob command to run all source files through tsx to node test runner "test:node": "glob -c \"node --import tsx --test\" \"./src/**/*.node.test.ts\"",
- Summary - Jest, not finding tests and likely issues with mocking.
Webpack
- Had to add use of NODE_OPTIONS=--openssl-legacy-provider. Webpack 4 said to not fix this.
- Webpack CLI may not support esm? https://stackoverflow.com/questions/64944796/webpack-5-and-esm
- https://github.com/firebase007/webpack-demo/blob/master/webpack.config.js
- https://stackoverflow.com/questions/50976936/how-to-get-dynamic-imports-to-work-in-webpack-4
ESBuild
- esm web app part 1 - https://how-to.dev/how-to-start-building-a-project-with-esbuild, part 2 https://how-to.dev/how-to-set-up-a-dev-server-with-esbuild
- How to dynamically import reports from App.tsx? https://how-to.dev/how-to-lazy-load-with-esbuild
- esbuild + ESM + NodeJS + Typescript troubles evanw/esbuild#3637 - esbuild + ESM + NodeJS + Typescript
- Just discards the TS type annotations, still need to run tsc -noEmit in parallel with esbuild to check types
- Add target of last 2 version or similar
- Address dynamic import of language locale
- Address Node Worker loading, no first-class support yet
  - WebWorker support? evanw/esbuild#312
  - threads.js alternatives - Typescript workers don't work with ESM andywer/threads.js#434
- https://gist.github.com/manzt/689e4937f5ae998c56af72efc9217ef0
AWS
- https://aws.amazon.com/blogs/compute/using-node-js-es-modules-and-top-level-await-in-aws-lambda/
- How to get esm enabled for gp functions? Need to use .mjs extension? Need to switch to nodejs lambda with esbuild, that perhaps looks at package.json for type module and does the right thing?
- https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda_nodejs-readme.html
- https://aws.amazon.com/blogs/compute/using-node-js-es-modules-and-top-level-await-in-aws-lambda/
- Current lambda construct, via use of runtime and code property - https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda-readme.html
- CDK use of ESM - (aws-lambda-nodejs): .mjs file extension and import.meta not supported aws/aws-cdk#13274
- Rewrite require() calls of Node built-ins to import statements when emitting ESM for Node evanw/esbuild#2067 (comment)
- Rewrite require() calls of Node built-ins to import statements when emitting ESM for Node evanw/esbuild#2067
- https://stackoverflow.com/questions/67361096/how-can-i-zip-node-lambda-dependencies-in-aws-cdk-stack
- Solutions required
  - build a mini package for each bundled lambda handler function with a package.json (type: module, with main entry point to the handler function). This will enable ESM and ensure handler function is found.
  - Add some esbuild workaround for use of require (banner js). And include entire aws-sdk in the build because v2 is not included already in nodejs lambda. only v3. Need to filter out this dependency after upgrade to v3.
- Storybook
  - https://storybook.js.org/docs/api/main-config-indexers
  - [RFC] Deprecate StoriesOf storybookjs/storybook#23177

- update typescript and ts-node config - file path and extension changes - migrate away from styled-icons/boxicons due to typing issue with esm - update flatgeobuf, remove old workarounds - add skipLibCheck to resolve flatgeobuf internal import error - update turf to v7 prerelease, migrate to exporting latest geojson types, tighten up geometry generics - ignore rbush type import errors - switch from ts-node to tsx for prepare script - migrating use of __dirname to new method

…ports

…port. Migrate use of require in some places, enough to get init working.

… extension

* start switch to vitest * drop jest stuff, other dirname and import dep fixes, reset lerna.json * use default-import to use and extend rbush * add vitest dep formally, add vitest-setup loading jest-dom * Migrate more tests, make them runnable standalone in vscode debug with direct import * update geoblaze, update overlap output changes related to turf area. skip many remaining tests * fix prepare * comment out and skip tests with jest mocks * initial migrate of scripts to vitest, skipping failing precalc datasource tests * stub vitest project runner * clean up vitest config type error, and punt on browser test mock error and bump vi* versions * skip remaining failing tests, add back test commit gate * try making vitest regular dependency * update runner to config project vitest * merge cli options * fix vitest cli command * switch to TEST_ROOT env var * shift jsdom dep for project use * fix TEST_ROOT * simplify test commands, tune test config * update vitest comments * add data server back to test command * vitest comments * drop ts-node for tsx * add testing of base and template packages, skipping most. Migrate remaining commands to vitest. Migrate to turf 7 in projects

…rce not fetching properly?

…cker workspace

…ded datasource fetch also resolved.

…etch polyfill

* convert function builder to esbuild * fix other function output dir, cleanup negative zero in cleanCoords * add buildClient using esbuild with html plugin, refactor App to receive lazy loaded report clients, fix loose client-ui exports * add esbuild polyfill, address esbuild strict module import - pare down projectClient import paths, switch client away from using top-level gp lib import, shift top-level indexes to prevent pollution of node code in ui code, guard use of process env var * Switch to generating ReportApp.tsx in .build-web with lazy load of report clients * on build copy language assets to .build-web

* upgrade aws-cdk-lib and aws-sdk, add package.json to build to get esm enabled in lambda, move esbuild dep to top of monorepo, add node 20 runtime * update data scripts to work in monorepo * fix precalc script env * build - create isolated mini package per function with own entry point. Add type assertion to language json import

…larify build script

…extract, add client polyfill globals process true

…es in directories. Fix dynamic import of translations in browser client

…18n dir

…ath .build

twelch · 2024-04-20T01:06:35Z

Upgrade WSL Ubunto to 22.04 Jammy

https://askubuntu.com/questions/1428423/upgrade-ubuntu-in-wsl2-from-20-04-to-22-04
upgrade postgres packages from 12.x to 14.x then run the cluster upgrade
upgrade GDAL

…in project

…outside of current directory

…s to older assert syntax but should change at some point

- polygon-clipping upgrade resulted in additional vertice in some clip results slightly changing value (<.04 sq meters). - Update base translations. Fix translations extract with babel import assertion plugin.

…tributes to pass to components

* switch to transient prop for duration ProgressBar * start conversion to Vite for client build, still need to fix import attributes and add dev server * Migrate start:client to Vite, language dynamic import not working or keeping with:json import assertion * Migrate gp lib to storybook 8 using Vite, missing project storybook still * drop babel from gp vite config, causing require error * add back storybook to build docs * migrate from start-storybook to just storybook * refactor report stories to use code generator with story-cache * add story-cache to base project gitignore * change report-stories to example-stories. Migrate templates to use them. reports required to use named export * migrate create:report to node 20 patterns. Fix classColumn type error * glob delete story caches on startup, add vite types using d.ts file for asset import * switch to Vite glob loader for language modules * no need to copy language modules into build-web anymore * add vite to base-project * export pathUtils, simplify tsconfig * Drop unused TranslatorSync component * shift storybook to dependencies for project user * Change story folder structure * Add turf/helpers to base-project since common project use * add all to dependencies to try and solve storybook start error * export datasource helpers, remove unused vitest workspace, update min node and npm in package.json * Make project storybook+vite independent of gp version * make styled-components props transient, drop unused main from base-project package.json * vite configure web worker * remove vite worker config since web worker not being used * fix story sort order * fix blank-project functions * attempt fix to favicon install command * add storybook install script for migraters. Add initial Migrating docs * add back default export to report clients require for React.lazy load

… esm

…book 8 (#272) * - update lerna and node, add eslint esm preset - update typescript and ts-node config - file path and extension changes - migrate away from styled-icons/boxicons due to typing issue with esm - update flatgeobuf, remove old workarounds - add skipLibCheck to resolve flatgeobuf internal import error - update turf to v7 prerelease, migrate to exporting latest geojson types, tighten up geometry generics - ignore rbush type import errors - switch from ts-node to tsx for prepare script - migrating use of __dirname to new method * switch CI to use node 20 * Migrate base-project and template packages to esm * disable run of test suite on commit until resolved * missed test * fix fetchPolyfill import * switch to nodenext module and moduleResolution. Add assert to json imports * clean up import of CJS dependencies that don't have a true default import. Migrate use of require in some places, enough to get init working. * switch to tsx for translation extract and migrate babel config to cjs extension * fix report name for template-blank-project * Switch from Jest to Vitest (#273) * start switch to vitest * drop jest stuff, other dirname and import dep fixes, reset lerna.json * use default-import to use and extend rbush * add vitest dep formally, add vitest-setup loading jest-dom * Migrate more tests, make them runnable standalone in vscode debug with direct import * update geoblaze, update overlap output changes related to turf area. skip many remaining tests * fix prepare * comment out and skip tests with jest mocks * initial migrate of scripts to vitest, skipping failing precalc datasource tests * stub vitest project runner * clean up vitest config type error, and punt on browser test mock error and bump vi* versions * skip remaining failing tests, add back test commit gate * try making vitest regular dependency * update runner to config project vitest * merge cli options * fix vitest cli command * switch to TEST_ROOT env var * shift jsdom dep for project use * fix TEST_ROOT * simplify test commands, tune test config * update vitest comments * add data server back to test command * vitest comments * drop ts-node for tsx * add testing of base and template packages, skipping most. Migrate remaining commands to vitest. Migrate to turf 7 in projects * fix type error, upgrade node-fetch, fix launcher paths, VectorDatasource not fetching properly? * add new world fgb and confirm test passing with latest unstable gp docker workspace * downgrade flatgeobuf to resolve timeout error, add back skipped tests * migrate to new import.meta.dirname available with node 20.12 * update fetch polyfill and upgrade again to latest flatgeobuf. subdivided datasource fetch also resolved. * unskip remaining tests utilizing flatgeobuf, update sideEffects for fetch polyfill * Switch to esbuild (#278) * convert function builder to esbuild * fix other function output dir, cleanup negative zero in cleanCoords * add buildClient using esbuild with html plugin, refactor App to receive lazy loaded report clients, fix loose client-ui exports * add esbuild polyfill, address esbuild strict module import - pare down projectClient import paths, switch client away from using top-level gp lib import, shift top-level indexes to prevent pollution of node code in ui code, guard use of process env var * Switch to generating ReportApp.tsx in .build-web with lazy load of report clients * on build copy language assets to .build-web * bring back template smoke tests * AWS - deploy pure ESM code for Lambda and client, on node 20 (#279) * upgrade aws-cdk-lib and aws-sdk, add package.json to build to get esm enabled in lambda, move esbuild dep to top of monorepo, add node 20 runtime * update data scripts to work in monorepo * fix precalc script env * build - create isolated mini package per function with own entry point. Add type assertion to language json import * upgrade zx, refactor translation install and extract to use scripts clarify build script * add missing esbuild plugins add missing babel plugin for translation extract, add client polyfill globals process true * cleanup isHostedOnLambda * process empty * bump * directly set client lambda env vars * add esbuild metafile output * add ANALYZE env vars * fix metafile output path * Switch to gp core imports in client to not pull backend modules * Allow minify to be overridden, defaults to true * fix minify arg passing * add cloufront access to client bucket to be able to access client files in directories. Fix dynamic import of translations in browser client * update translationInstall to be more comprehensive * update dirname in importTerms and publishTerms, loosen gitignore on i18n dir * Make sure .build dir created, remove old createManifest * bump * simplify generateHandler, add guard to .build dir copy * Cut out intermediate build in gp .build dir, go straight to project path .build * simplify build client gp path discovery * make build client use gp dependencies. removes need for esbuild deps in project * replace use of esbuild-plugin-html which doesn't support entry point outside of current directory * upgrade to typescript 5.4.5 * swtich from assert json to with json * fully switch from assert to with import syntax, esbuild still converts to older assert syntax but should change at some point * rebuild package lockfile, major non-breaking npm upgrades * additional upgrades: - polygon-clipping upgrade resulted in additional vertice in some clip results slightly changing value (<.04 sq meters). - Update base translations. Fix translations extract with babel import assertion plugin. * upgrade babel proposal plugins to official * update husky prepare command, husky install is deprecated * migrate to new styled-components .attrs() to define caller-defined attributes to pass to components * switch to transient prop for duration ProgressBar * Vite for client dev, build, storybook (#282) * switch to transient prop for duration ProgressBar * start conversion to Vite for client build, still need to fix import attributes and add dev server * Migrate start:client to Vite, language dynamic import not working or keeping with:json import assertion * Migrate gp lib to storybook 8 using Vite, missing project storybook still * drop babel from gp vite config, causing require error * add back storybook to build docs * migrate from start-storybook to just storybook * refactor report stories to use code generator with story-cache * add story-cache to base project gitignore * change report-stories to example-stories. Migrate templates to use them. reports required to use named export * migrate create:report to node 20 patterns. Fix classColumn type error * glob delete story caches on startup, add vite types using d.ts file for asset import * switch to Vite glob loader for language modules * no need to copy language modules into build-web anymore * add vite to base-project * export pathUtils, simplify tsconfig * Drop unused TranslatorSync component * shift storybook to dependencies for project user * Change story folder structure * Add turf/helpers to base-project since common project use * add all to dependencies to try and solve storybook start error * export datasource helpers, remove unused vitest workspace, update min node and npm in package.json * Make project storybook+vite independent of gp version * make styled-components props transient, drop unused main from base-project package.json * vite configure web worker * remove vite worker config since web worker not being used * fix story sort order * fix blank-project functions * attempt fix to favicon install command * add storybook install script for migraters. Add initial Migrating docs * add back default export to report clients require for React.lazy load * nit Migrating

twelch added 2 commits March 6, 2024 16:53

switch CI to use node 20

8e840a7

twelch marked this pull request as draft March 7, 2024 03:04

twelch self-assigned this Mar 13, 2024

twelch added 19 commits March 12, 2024 22:45

Migrate base-project and template packages to esm

1e5b15d

disable run of test suite on commit until resolved

4e2faad

missed test

4f79454

fix fetchPolyfill import

1732fe8

switch to nodenext module and moduleResolution. Add assert to json im…

bd13d38

…ports

clean up import of CJS dependencies that don't have a true default im…

34d7010

…port. Migrate use of require in some places, enough to get init working.

switch to tsx for translation extract and migrate babel config to cjs…

399b10f

… extension

fix report name for template-blank-project

001c32d

fix type error, upgrade node-fetch, fix launcher paths, VectorDatasou…

cf2e533

…rce not fetching properly?

add new world fgb and confirm test passing with latest unstable gp do…

2391c0a

…cker workspace

downgrade flatgeobuf to resolve timeout error, add back skipped tests

49028a5

migrate to new import.meta.dirname available with node 20.12

d9a3223

update fetch polyfill and upgrade again to latest flatgeobuf. subdivi…

a9b5561

…ded datasource fetch also resolved.

unskip remaining tests utilizing flatgeobuf, update sideEffects for f…

a69708a

…etch polyfill

Merge branch 'dev' into esm and make esm-compatible

8c202b1

bring back template smoke tests

6b745bf

twelch changed the title ~~Migrate to ES Module structure~~ Migrate to ES Module structure, Node 20, Vitest, esbuild Apr 17, 2024

twelch added 6 commits April 18, 2024 11:06

upgrade zx, refactor translation install and extract to use scripts c…

79370fc

…larify build script

add missing esbuild plugins add missing babel plugin for translation …

92f6bcb

…extract, add client polyfill globals process true

cleanup isHostedOnLambda

233223f

process empty

881eff6

bump

0f86ee5

directly set client lambda env vars

3cbf0ff

twelch added 7 commits April 19, 2024 10:07

add cloufront access to client bucket to be able to access client fil…

43673c4

…es in directories. Fix dynamic import of translations in browser client

update translationInstall to be more comprehensive

6e78970

update dirname in importTerms and publishTerms, loosen gitignore on i…

dd550c8

…18n dir

Make sure .build dir created, remove old createManifest

144bbbf

bump

62bc5bc

simplify generateHandler, add guard to .build dir copy

ee804e7

Cut out intermediate build in gp .build dir, go straight to project p…

778f3be

…ath .build

twelch added 12 commits April 21, 2024 19:59

simplify build client gp path discovery

cb7503a

make build client use gp dependencies. removes need for esbuild deps …

414afdb

…in project

replace use of esbuild-plugin-html which doesn't support entry point …

2a337a8

…outside of current directory

upgrade to typescript 5.4.5

ef6ce5e

swtich from assert json to with json

631d985

fully switch from assert to with import syntax, esbuild still convert…

6577438

…s to older assert syntax but should change at some point

rebuild package lockfile, major non-breaking npm upgrades

dd819c9

additional upgrades:

feec025

- polygon-clipping upgrade resulted in additional vertice in some clip results slightly changing value (<.04 sq meters). - Update base translations. Fix translations extract with babel import assertion plugin.

upgrade babel proposal plugins to official

25ba9b8

update husky prepare command, husky install is deprecated

735b82f

migrate to new styled-components .attrs() to define caller-defined at…

d9d4076

…tributes to pass to components

switch to transient prop for duration ProgressBar

b0cd88e

twelch mentioned this pull request May 9, 2024

Version 7.0 #285

Open

twelch changed the title ~~Migrate to ES Module structure, Node 20, Vitest, esbuild~~ Migrate to ES Module structure/runtime - Node 20, Vite, Vitest, Storybook 8 May 14, 2024

twelch marked this pull request as ready for review May 14, 2024 00:35

twelch added 2 commits May 14, 2024 10:07

Merge branch 'esm' of https://github.com/seasketch/geoprocessing into…

bdb4a99

… esm

nit Migrating

7c6bb19

twelch merged commit 649fb9e into dev May 14, 2024
2 checks passed

twelch deleted the esm branch May 14, 2024 18:22

twelch mentioned this pull request Jul 31, 2024

Migrate gp library to pure ESM #122

Closed

14 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Migrate to ES Module structure/runtime - Node 20, Vite, Vitest, Storybook 8 #272

Migrate to ES Module structure/runtime - Node 20, Vite, Vitest, Storybook 8 #272

twelch commented Mar 7, 2024 •

edited

Loading

twelch commented Apr 20, 2024

Migrate to ES Module structure/runtime - Node 20, Vite, Vitest, Storybook 8 #272

Migrate to ES Module structure/runtime - Node 20, Vite, Vitest, Storybook 8 #272

Conversation

twelch commented Mar 7, 2024 • edited Loading

Dev

ToDo

Questions

Notes on steps

twelch commented Apr 20, 2024

twelch commented Mar 7, 2024 •

edited

Loading