A way to change the NODE_ENV in targets?

[jjenzz]

I need to expose a production and development bundle with my package so that during development, consumers will get feedback from us for various things.

I thought I would be able to use targets for this, so I created something like this:

{
  "main": "dist/index.js",
  "module": "dist/pkg.module.min.js",
  "development": "dist/pkg.development.js",
  "types": "dist/index.d.ts",
  "targets": {
    "development": {
      "minify": false,
      "outputFormat": "global",
      "scopeHoist": false,
      "isLibrary": true
    }
  },
  "scripts": {
    "build": "parcel build src/index.ts --no-cache && yarn build:entry",
    "build:entry": "yarn build:entry:rename && cp ../scripts/entry.js dist/index.js",
    "build:entry:rename": "mv dist/index.js dist/pkg.production.min.js && mv dist/index.js.map dist/pkg.production.min.js.map",
  },
}

(entry.js switches which module to load based on env)

However, parcel will expectedly build the pkg.development.js file with NODE_ENV=production so dev logging is stripped. I tried to run two builds for each env but it slows things down quite a bit (we have a lot of packages) and it builds development target twice unnecessarily.

"build": "yarn build:prod && yarn build:dev && yarn build:styles && yarn build:entry",
"build:prod": "parcel build src/index.ts --no-cache",
"build:dev": "NODE_ENV=development parcel build src/index.ts --no-cache --target development",

This added around an extra 4s to each package build 😬

I feel like there must be a better way to handle this. Is anyone able to help me solve this? 🙏

---

Note: We have to use --no-cache for our builds because we keep getting old versions of our code in our built packages otherwise. With the --target development example above, if we don't use --no-cache it will output production code even though the env is development.

---