Fix tree shaking

[0x009922]

Changes

• Remove a lot of unnecessary SFC names declaration
• ui library now has unit & after-build tests driven by vitest
• After-build tests ensure tree-shakeability, e.g. library does not have any side-effects.

For other details please see changesets.

Explorations

• TypeScript enums are evil. They are not tree-shakeable because they are compiled to IIFE:

  enum Status {
    Info
  }

  var Status;
  (function (Status) {
    Status[Status["Info"] = 0] = "Info";
  })(Status || (Status = {}));

  The way I used to work-around it:

  export const Status = {
    Info: 'info',
    Success: 'success',
    Warning: 'warning',
    Error: 'error',
  } as const
  
  export type Status = typeof Status[keyof typeof Status]
  
  function acceptAnyStatus(status: Status) {}
  
  acceptAnyStatus(Status.Error)
  
  function acceptInfoOnly(info: typeof Status.Info) {}
  
  acceptInfoOnly(Status.Info)

• jsoneditor and lodash (**edit:**not sure) are evil. They have side-effects. Fortunately, they are only used within SJsonInput. I excluded this component from the bundle temporarily - anyway it is unused and out of design system.

• body-scroll-lock is evil too, but only a bit. It has a small side-effect check code. I think it can be implemented in pure manner, and maybe I'll open a PR. upd: The package is not tree-shakeable due to side-effects willmcpo/body-scroll-lock#254 and Fix tree shake by adding some /* @__PURE__ */ marks willmcpo/body-scroll-lock#255
  For now, I exclude it from SModal component, but I add a new component - SBodyScrollLockProvider. SModal will use it's locker by default. For details please see sources and SModal.spec.cy for usage example (it uses body-scroll-lock small wrap).

• defineComponent() should always be used with /* @__PURE__ */ or /* #__PURE__ */ prefix. Generally, it should be avoided.

• vite.config.ts → build.target set to esnext. It produces more pure code, and in some cases it matters for tree-shaking.
  The exact case is the following:

  • SFC with 2 <script lang="ts"> blocks;

  • Some component options:

    export default {
      inheritAttrs: false
    }

  As a result, without esnext target there is a dirt that prevents component to be tree-shaken.

[0x009922]

name var could be a Symbol. TypeScript prevented runtime error!

[0x009922]

Make in-source tests possible.

[0x009922]

Will be useful when there some in-source tests appear.

[Ctepan]

There are new components, so it's necessary to make same operations to them