JuliaDocs/Documenter.jl

Reconsider how we deploy JS assets (aka. let's get rid of RequireJS)

Open

#2,158 创建于 2023年6月29日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)Julia (910 star) (513 fork)batch import
Format: HTMLType: Enhancementhelp wanted

描述

Right now, we take all the .js files from here and "compile" them into a single JS file where each of them also gets wrapped in a RequireJS require call. The idea here, back in the day, was to separate the JS snippets from each other (e.g. so that you wouldn't get variable name clashes), and to manage their dependencies.

But RequireJS is a bit dated, and is slowly starting to cause problems. Not all JS libraries are ameanable to it anymore, for example.

This is low-priority, but we should think how to architect a better system here that keeps the two properties: (1) Isolation of the different modules, and (2) still allows us to manage dependencies somehow (e.g. that we wouldn't just load multiple versions of the same library). Maybe we can use native JS modules or something nowadays?

X-refs:

  • #1247
  • #1433
  • #2471
  • #1433
  • #2702

贡献者指南

技术栈
javascript
领域
frontendbuild system
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Understanding of JavaScript modulesFamiliarity with RequireJSKnowledge of JavaScript build tools
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
Look into alternatives to RequireJS for bundling JavaScript modules, such as ES modules with a bundler like Rollup or Webpack. Consider how to maintain module isolation and dependency management. Check existing issues #1247, #1433, #2471, #2702 for prior discussions. Propose a concrete architecture change.