About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community_call:minutes20221101

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
community_call:minutes20221101 [2022/11/01 13:16] – [1. Development Planning] demiankatzcommunity_call:minutes20221101 [2022/11/01 13:40] (current) – [2. Technology Demo for Javascript Tooling Planning] demiankatz
Line 61: Line 61:
 ==== 2. Technology Demo for Javascript Tooling Planning ==== ==== 2. Technology Demo for Javascript Tooling Planning ====
  
 +Chris proposed using package.json scripts instead of using Grunt (which is no longer widely used and is somewhat hard to understand). Some tasks will "just work" (like eslint, which is a simple command that loads a default configuration file), but other tasks may require custom scripts (like less/sass, which needs to account for our theme inheritance, etc.). Chris proposes adding a "scripts" directory to hold these scripts.
 +
 +Chris also raised the issue of Javascript modernization -- should we use React, Vue.js, Typescript, etc. Possible compromise that could improve code quality without increasing complexity of deployment/development: annotate files using jsdoc for types, then use Typescript's tsc to validate the files. Offers a possible "best of both worlds" solution.
 +
 +Next steps: Chris will set up a PR to begin the grunt --> npm conversion, starting with SCSS compilation (which Claas will help test).
 ==== 3. Other Topics? ==== ==== 3. Other Topics? ====
  
community_call/minutes20221101.1667308619.txt.gz · Last modified: 2022/11/01 13:16 by demiankatz