in-publish | Detect if we were run as a result of npm publish | Runtime Evironment library

I'm trying to use ProGuard to minimize my gradle plugin and it works well, producing the output file a-min.jar

However, com.gradle.plugin-publish plugin just doesn't recognize it when using task publishPlugins, it tells

Cannot determine main artifact to upload - could not find jar artifact with empty classifier

Strangely, when using publishToMavenLocal it did work well.

I've tried some tricks to replace the main jar with my processed jar, but always failed. Is there any new sight here?

On npm I read:

To help developers who rely on your code, we recommend starting your package version at 1.0.0 and incrementing as follows:

Assuming that the way packages are actually versioned in the real world matches the above recommendation; when they use the ambiguous word "incrementing", do they mean to recommend:

1. The next release to be versioned either 1.0.1, 1.1.0 or 2.0.0
2. The next release to be versioned anything greater than 1.0.0 (e.g. even 1.0.9)

Relevant example:

You have "your-package" published on npm as v1.0.0
You work on it, refactor the code, fix a bunch of bugs and tag the last commit as v1.0.1
Then you notice a serious bug and after fixing it, you put a v1.0.2 tag

Now you decide to publish a release, if you was to publish the release as v1.0.2 (without a v1.0.1 ever being published) would you be going against npm recommendation?

According to this post, custom post type, hide or disable the trash button in publish meta box, this is specifically removing for post. I couldn't find any post solutions relating to remove 'Move to trash' under woocommerce order action. Does this code apply same to removing this button on woocommerce?

I am testing the sample code of javascript.

There is script like simple.js under demos directory.

I run demo by this command yarn build-demos && http-server demos/

simple.js is compiled to simple_bundle.js and server works.

However everytime I change simple.js, I need to restart server.

Is there any good short cut for this purpose??

I am not familiar with npm and webpack

Any help is appreciated.

My package.json is here below:

I'm attempting to upgrade a grails plugin from grails version 4.0.3 to 4.0.11 and get the following error immediately after changing the grails and GORM versions:

I'm using nz-input textarea in 'nz-form' form.

I don't know how to make textarea fit its parent's height.

Demo

Here is the status quo:

What I want is:

I know what the problem is

If I directly set style="height:100%" for the two div and textarea, then I can get the target. But, the two div actually are not on my component's template html. So, I do not know how to fix this issue. I've tried to override the 'ant-form-item-control-input-content' css class, but it did not work.