Releases: tdeekens/promster
@promster/[email protected]
Patch Changes
-
39dbcfa#553 Thanks @renovate! - chore(deps): update dependency @hapi/boom to v9.1.1 -
Updated dependencies [
daf8605]:- @promster/[email protected]
@promster/[email protected]
Patch Changes
- Updated dependencies [
daf8605]:- @promster/[email protected]
@promster/[email protected]
Patch Changes
- Updated dependencies [
daf8605]:- @promster/[email protected]
@promster/[email protected]
Major Changes
-
0eb64ca#529 Thanks @tdeekens! - # Introductionrefactor: to use preconstruct for building
Prior TypeScript was used to build bundles. In all this should not affect consumers of this library. Under the hood preconstruct uses rollup and babel which is now instructed to build for Node.js v12 using the preset-env preset.
Breaking Change
This release can potentially be breaking for you. We want to respect semantic versioning and follow it strictly.
While migrating to preconstruct the
versionexports had to be removed as preconstruct's rollup will not resolve them. If you relied on this value you should either load thepackage.jsonof each module yourself or drop the usage.- const { version } = require('@promster/server'); + const { version } = require('@promster/server/package.json');
Patch Changes
@promster/[email protected]
Major Changes
-
0eb64ca#529 Thanks @tdeekens! - # Introductionrefactor: to use preconstruct for building
Prior TypeScript was used to build bundles. In all this should not affect consumers of this library. Under the hood preconstruct uses rollup and babel which is now instructed to build for Node.js v12 using the preset-env preset.
Breaking Change
This release can potentially be breaking for you. We want to respect semantic versioning and follow it strictly.
While migrating to preconstruct the
versionexports had to be removed as preconstruct's rollup will not resolve them. If you relied on this value you should either load thepackage.jsonof each module yourself or drop the usage.- const { version } = require('@promster/server'); + const { version } = require('@promster/server/package.json');
Patch Changes
@promster/[email protected]
Major Changes
-
0eb64ca#529 Thanks @tdeekens! - # Introductionrefactor: to use preconstruct for building
Prior TypeScript was used to build bundles. In all this should not affect consumers of this library. Under the hood preconstruct uses rollup and babel which is now instructed to build for Node.js v12 using the preset-env preset.
Breaking Change
This release can potentially be breaking for you. We want to respect semantic versioning and follow it strictly.
While migrating to preconstruct the
versionexports had to be removed as preconstruct's rollup will not resolve them. If you relied on this value you should either load thepackage.jsonof each module yourself or drop the usage.- const { version } = require('@promster/server'); + const { version } = require('@promster/server/package.json');
Patch Changes
@promster/[email protected]
Major Changes
-
0eb64ca#529 Thanks @tdeekens! - # Introductionrefactor: to use preconstruct for building
Prior TypeScript was used to build bundles. In all this should not affect consumers of this library. Under the hood preconstruct uses rollup and babel which is now instructed to build for Node.js v12 using the preset-env preset.
Breaking Change
This release can potentially be breaking for you. We want to respect semantic versioning and follow it strictly.
While migrating to preconstruct the
versionexports had to be removed as preconstruct's rollup will not resolve them. If you relied on this value you should either load thepackage.jsonof each module yourself or drop the usage.- const { version } = require('@promster/server'); + const { version } = require('@promster/server/package.json');
Patch Changes
@promster/[email protected]
Major Changes
-
0eb64ca#529 Thanks @tdeekens! - # Introductionrefactor: to use preconstruct for building
Prior TypeScript was used to build bundles. In all this should not affect consumers of this library. Under the hood preconstruct uses rollup and babel which is now instructed to build for Node.js v12 using the preset-env preset.
Breaking Change
This release can potentially be breaking for you. We want to respect semantic versioning and follow it strictly.
While migrating to preconstruct the
versionexports had to be removed as preconstruct's rollup will not resolve them. If you relied on this value you should either load thepackage.jsonof each module yourself or drop the usage.- const { version } = require('@promster/server'); + const { version } = require('@promster/server/package.json');
Patch Changes
@promster/[email protected]
Major Changes
-
0eb64ca#529 Thanks @tdeekens! - # Introductionrefactor: to use preconstruct for building
Prior TypeScript was used to build bundles. In all this should not affect consumers of this library. Under the hood preconstruct uses rollup and babel which is now instructed to build for Node.js v12 using the preset-env preset.
Breaking Change
This release can potentially be breaking for you. We want to respect semantic versioning and follow it strictly.
While migrating to preconstruct the
versionexports had to be removed as preconstruct's rollup will not resolve them. If you relied on this value you should either load thepackage.jsonof each module yourself or drop the usage.- const { version } = require('@promster/server'); + const { version } = require('@promster/server/package.json');
Patch Changes
@promster/[email protected]
Major Changes
-
0eb64ca#529 Thanks @tdeekens! - # Introductionrefactor: to use preconstruct for building
Prior TypeScript was used to build bundles. In all this should not affect consumers of this library. Under the hood preconstruct uses rollup and babel which is now instructed to build for Node.js v12 using the preset-env preset.
Breaking Change
This release can potentially be breaking for you. We want to respect semantic versioning and follow it strictly.
While migrating to preconstruct the
versionexports had to be removed as preconstruct's rollup will not resolve them. If you relied on this value you should either load thepackage.jsonof each module yourself or drop the usage.- const { version } = require('@promster/server'); + const { version } = require('@promster/server/package.json');