Skip to content

v1.6.1

Latest

Choose a tag to compare

@Aejkatappaja Aejkatappaja released this 31 Jul 09:11
· 2 commits to main since this release
3d58d99

A packaging fix for people who vendor the library instead of installing it. No change for anyone using npm or the CDN: phantom-ui.js and phantom-ui.cdn.js are byte-identical to 1.6.0.

Fixed

The release assets now pair correctly. TypeScript resolves a declaration file to a module by exact filename, so the unminified build added in 1.6.0 was arriving with no types at all: it was named phantom-ui.standalone.dev.js and looked for a .dev.d.ts that does not exist.

The assets attached to this release are:

phantom-ui.standalone.js      unminified, about 1500 lines, readable
phantom-ui.standalone.min.js  the same code, minified
phantom-ui.standalone.d.ts    types, no imports of any kind

Download the first and the third into a folder and import by path. Nothing else to configure, and it type-checks under strict with skipLibCheck: false in a project with no node_modules at all.

Heads up if you took the 1.6.0 asset: phantom-ui.standalone.js changes form here. It was the minified build, it is now the unminified one. Same code, larger file. Take phantom-ui.standalone.min.js if you want the small one.

Using it in Angular

Two things that are easy to lose time on, neither specific to this release:

import { CUSTOM_ELEMENTS_SCHEMA } from "@angular/core";
// ...
schemas: [CUSTOM_ELEMENTS_SCHEMA],

Without it Angular rejects the tag with NG0304. And bind through the attribute rather than the property:

<phantom-ui [attr.loading]="loading() ? '' : null">