Sly777/ran

RAN as NPM dependency

Open

#44 opened on 2017年7月13日

GitHub で見る
 (8 comments) (0 reactions) (0 assignees)JavaScript (2,203 stars) (180 forks)batch import
enhancementhelp wanted

説明

Would there be any chance of releasing RAN as an NPM dependency usable in our projects similar to next.js? When cloning the project, we are importing all of the complexity into our own codebase, are left on our own for maintenance, and can't benefit from future updates made to this project.

Thanks for your time 🙂

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

技術スタック
javascriptreactgraphqlnextjsnodejs
領域
developer experiencetooling
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
3-5 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
なし
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
25
調査方針
This issue requests that RAN be made available as an npm package, similar to Next.js, to allow developers to use it as a dependency without cloning the entire repository. To implement this, one would need to analyze the current project structure and build setup, likely involving creating a separate package that exports the core functionalities (e.g., React components, GraphQL utilities, CLI commands). Key files to examine include the package.json, any build scripts, and the source code structure. There are no linked PRs, so the first step would be to outline a plan for modularization and npm publishing.