parcel-bundler/parcel

Improve error message, when having nightly and standard packages in package.json at the same time

Open

#7946 opened on Apr 13, 2022

View on GitHub
 (4 comments) (0 reactions) (0 assignees)JavaScript (44,030 stars) (2,274 forks)batch import
:raising_hand_woman: FeatureGood First Issue

Description

🐛 bug report

parcel build doesn't work

🎛 Configuration (.babelrc, package.json, cli command)

package.json:

"@parcel/config-webextension": "^2.4.2-nightly.2666",
"@parcel/reporter-bundle-analyzer": "^2.4.1",
"@parcel/transformer-typescript-tsc": "^2.4.1",
"parcel": "^2.4.1"

{
  "extends": "@parcel/config-webextension",
}

🤔 Expected Behavior

builds ok

😯 Current Behavior

errors out:

> build:dev
> NODE_ENV=development parcel build src/entry/manifest.json --log-level verbose && date +"%T"

[ThrowableDiagnostic [Error]: The plugin "@parcel/reporter-dev-server" is not compatible with the current version of Parcel. Requires "2.0.0-nightly.1041+39b330e74" but the current version is "2.4.1".] {
  diagnostics: [
    {
      message: 'The plugin "@parcel/reporter-dev-server" is not compatible with the current version of Parcel. Requires "2.0.0-nightly.1041+39b330e74" but the current version is "2.4.1".',
      origin: '@parcel/core',
      codeFrames: [Array]
    }
  ]
}

💁 Possible Solution

fix the deps in @parcel\core

🌍 Your Environment

Software Version(s)
Parcel 2.4.1
Node 17.3.0
npm/Yarn npm 8.3.0
Operating System macOS 12.3

Contributor guide

Tech stack
javascriptnodejs
Domain
build system
Issue type
bug
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.
1-3 hours
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.
mostly clear
Prerequisites
understanding of npm semver rangesbasic Parcel concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue is about improving the error message when both nightly and stable packages of Parcel are present. The error currently shows a version mismatch, but doesn't clearly indicate the root cause of mixing nightly and stable. A good fix would be to detect the combination and print a more helpful message, possibly in the @parcel/core package where plugins are validated. Look at the source code for plugin validation in the parcel core package (likely in packages/core/core/src/). The error originates from @parcel/reporter dev server, but the improvement should be in the validation logic. Also check if there are any guidelines on nightly vs stable usage in the documentation.