Add preprocess to published files array

[sebastianrothe]

add preprocess to published files

Fixes #81

[mihar-22]

Why did package-lock.json completely change? What version of NPM are you using? Prefer NPM >=7 to use v2 lockfiles. Is this related to something else? By the way maybe we should include the entire dist folder dist/?

[benmccann]

I agree that including the entire dist directory would be a better solution

[sebastianrothe]

Why did package-lock.json completely change? What version of NPM are you using? Prefer NPM >=7 to use v2 lockfiles. Is this related to something else? By the way maybe we should include the entire dist folder dist/?

Well I am using the latest npm v7 and lockfile v2. Someone else committed an old lockfile before.

[sebastianrothe]

@mihar-22 Please merge and publish a new version. I think this time it is correct :)

[sebastianrothe]

I agree that including the entire dist directory would be a better solution

I added one more commit.

[benmccann]

@mihar-22 it looks like you might be on npm 6. It got switched to the old lockfile format here: c59643a

Anyway, this looks good to me! Thanks for helping to work through these issues and get new versions out!

[sebastianrothe]

Somehow the lockfile is v1 again. Is NPM doing this?

[mihar-22]

Ah I know why... I always try to run the tests but they fail on Node 16/NPM 7 due to SASS compiler not working with that version on the new ARMx64 architecture. So after that fails I switch to Node 14 and it works. It's the only way I can verify tests. I'll move releases to CI to resolve this, but we need to ensure commits follow standard semantic-release conventions, so probabaly need to add commitlint.

[sebastianrothe]

The tests do run in the CI, too.

But a release from the CI would be very nice :)