Sly777/ran

RAN as NPM dependency

Open

#44 opened on Jul 13, 2017

View on GitHub
 (8 comments) (0 reactions) (0 assignees)JavaScript (2,203 stars) (180 forks)batch import
enhancementhelp wanted

Description

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 🙂

Contributor guide

Tech stack
javascriptreactgraphqlnextjsnodejs
Domain
developer experiencetooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
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.