ProjectEvergreen/greenwood

consolidate all internal rollup plugin usages to Rollup config

Open

#1,391 opened on Jan 19, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (1 assignee)JavaScript (15 forks)auto 404
CLIalpha.1enhancementgood first issuev0.35.0

Repository metrics

Stars
 (132 stars)
PR merge metrics
 (Avg merge 25d 20h) (29 merged PRs in 30d)

Description

Type of Change

Enhancement

Summary

Currently some Greenwood plugins provide their own Rollup plugins, but I think it would make more sense if those were all just declared "top level" in rollup.config.js since we're already doing that for other Rollup plugins like CommonJS and NodeJS resolution. I often forget that Greenwood has these Rollup plugins tucked away

Details

I think both of these just can get moved / imported into getRollupConfigForBrowserScripts

  1. Node Modules - https://github.com/ProjectEvergreen/greenwood/blob/v0.31.0-alpha.5/packages/cli/src/config/rollup.config.js#L577
  2. Terser - https://github.com/ProjectEvergreen/greenwood/blob/v0.31.0-alpha.5/packages/cli/src/plugins/resource/plugin-standard-javascript.js#L76

Contributor guide

Research direction
Examine the two referenced Rollup plugin usages and move them into the getRollupConfigForBrowserScripts function in rollup.config.js, ensuring all imports are correctly resolved.
Tech stack
javascript
Domain
backendbuild system
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rollup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70