rename stuff like options.js and /assets/ to names more sourcejs related · sourcejs/Source#229

(1 comment) (0 reactions) (0 assignees)JavaScript (552 stars) (49 forks)batch import

good first contributionhelp wanted

説明

Now that install by dependency is going to become the official way and the only way in 0.7.x I think we should think about being a bit less invasive upon people's environment.

Imagine if every npm dependency just asked to add a options.js to the root of the folder? I propose we rename it to something like sourcejs.config.js if that's possible.

Also I think all template-overrides, assets overrides and core-overrides could be in a sourcejs folder by default, instead of in the root. Another options would be to rename them to sourcejs-assets, sourcejs-templates.. etc.

コントリビューターガイド

技術スタック: javascriptnodejs
領域: frontenddeveloper experiencetooling
Issue 種別: refactor
難度: 2
推定時間: half day
活動状況: stale
明確さ: clear
前提条件: SourceJS project structurenpm package configurationJavaScript/Node.js basics
初心者向け度: 65
調査方針: Start by examining the current root directory for files like options.js and folders named assets, templates, core overrides. Identify all imports or references to these files and folders in the codebase, particularly in configuration files and module loading. Rename options.js to sourcejs.config.js and move overrides into a sourcejs/ subdirectory, updating all internal references. Check the repository's wiki or documentation for any mentions of these paths.