Reconsider how we deploy JS assets (aka. let's get rid of RequireJS) · JuliaDocs/Documenter.jl#2158

(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
難度: 3
預計時間: 3-5 days
活動狀態: stale
清晰度: mostly clear
前置要求: Understanding of JavaScript modulesFamiliarity with RequireJSKnowledge of JavaScript build tools
新手友善度: 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.