Parcel v2 doesnt ignore targets as specified in the docs

🐛 bug report

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

{
  "name": "test",
  "version": "1.0.0",
  "description": "Make the coffee",
  "author": "You",
  "license": "MIT",
  "main": "index.js",
  "targets": {
    "main": false
  },
  "engines": {
    "node": ">= 10.0.0"
  },
  "scripts": {
    "build": "parcel build ."
  },
  "devDependencies": {
    "parcel": "2.0.0-beta.1",
  }
}

🤔 Expected Behavior

According to https://v2.parceljs.org/configuration/package-json/#main-%2F-module-%2F-browser, parcel creates automatically a target for “main” if you specify it.

However you can disable it with:

  "targets": {
    "main": false
  },

It should disable the target, hence not try to build your code since there are no targets!

😯 Current Behavior

Parcel try to build your code.

🔦 Context

For monorepos, it would be nice to be able to disable the build for a package using this, or another flag. This way you can use for instance

yarn parcel build packages/*

and disable some packages you don’t want parcel to deal with. This would enable a progressive approach to adopt parcel as a build system for every packages.

💻 Code Sample

🌍 Your Environment

Software	Version(s)
Parcel	2.0.0-beta.1
Node	14
npm/Yarn	yarn 1.22.10
Operating System	linux

[paeolo]

@alphabet-codes Yes that was my expectation before @mischnic told me that was not the case. I came to that conclusion after reading https://v2.parceljs.org/configuration/package-json/#main-%2F-module-%2F-browser so maybe we could add something here in the docs precising how targets works.

or we could add someting in parcel code so it ignores some packages when you use a glob. Anyway, it’s already possible to do the second solution with a custom script, since you can call parcel build with a liste of packages.

[AceTheCreator]

@paeolo you’re welcome.