[QUESTION] How can I unset env variable when run npm script?

[DimaGashko]

What / Why

I have some npm scripts. Some of them use env variables. For example (just example):

"scripts": {
    "start": "webpack --watch --env.noSourceMaps",
  },

So, for now, when I call npm start env.noSourceMaps = true

But, how can I unset that variable when run npm start?

If I run npm run -- --env.noSourceMaps=false I got env.noSourceMaps = [true, 'false']

If I run npm run -- --env.noSourceMaps I got env.noSourceMaps = [true, true]

If I run npm run -- --env.noSourceMaps= I got env.noSourceMaps = [true, '']

But I want env.noSourceMaps = false or undefined

And I do not want to reverse logic (I mean, i don't want to use it as "start": "webpack --watch" and call it as npm start or npm start -- --env.noSouceMaps or "start": "webpack --watch", "start:noMaps": "webpack --watch --env.noSourceMaps")

[ljharb]

you can't, unless webpack allows you to do it.

[ljharb]

In other words, if you want to call a script with a passthrough arg, the script can't already have defined that arg.

[DimaGashko]

@ljharb Got it, Thanks for answering.