parcel-bundler/parcel

parcel build doesn't complain about nonexistent entry points

Open

#7486 opened on Dec 26, 2021

View on GitHub
 (9 comments) (0 reactions) (0 assignees)JavaScript (44,030 stars) (2,274 forks)batch import
:bug: Bug:pray: Help WantedGood First IssueStale IgnoreWindows

Description

🐛 bug report

Parcel silently ignores nonexistent entry points instead of showing some kind of error message.

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

No .babelrc, no package.json. Command:

parcel build this-file-doesnt-exist.html

🤔 Expected Behavior

Build should fail with an error message like "File not found: this-file-doesnt-exist.html".

😯 Current Behavior

The build completes "successfully":

$> parcel build this-file-doesnt-exist.html
✨ Built in 418ms

🌍 Your Environment

Software Version(s)
Parcel 2.0.1
Node v17.3.0
npm 8.3.0
Operating System Windows 10

Contributor guide

Tech stack
javascriptnodejs
Domain
clibuild systemdeveloper experience
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.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic JavaScriptNode.js file system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The fix involves adding a file existence check before processing the entry point in Parcel's CLI. Look at the `parcel build` command implementation; likely in `packages/core/core/src/CLI.js` or similar. Import `fs` and use `existsSync` to verify the entry file. If not found, throw an error with the message. Consider handling multiple entry points as well.