Skip to content
This repository has been archived by the owner on Nov 4, 2024. It is now read-only.

chore(deps): update dependency piral-cli-webpack5 to v1.7.1 #19

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 30, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
piral-cli-webpack5 (source) 1.0.1 -> 1.7.1 age adoption passing confidence

Release Notes

smapiot/piral (piral-cli-webpack5)

v1.7.1

Compare Source

  • Fixed engines field to have a constraint for Node.js >=18.17
  • Fixed release mode behavior of piral-vue3 reactivity (#​720)

v1.7.0

Compare Source

  • Fixed issue in piral-vue3 concerning reactivity of props (#​720)
  • Updated to latest version of dets
  • Updated website emulator to contain scaffolding tarballs
  • Updated pilets to automatically treat defined app shells as shared
  • Added support for shared key in piral.json

v1.6.2

Compare Source

  • Fixed registerBreadcrumbs in piral-breadcrumbs failing when no matcher was specified
  • Updated dependencies
  • Removed dependency to path-to-regexp package
  • Added loading-pilets and loaded-pilets events

v1.6.1

Compare Source

  • Improved CLI flag validation and documentation (#​705)
  • Added InjectionToken constants for compatibility with Angular's inject to piral-ng (#​703)

v1.6.0

Compare Source

  • Fixed event dispatching for providers in piral-blazor
  • Fixed navigation storm in angular pilets (#​672)
  • Fixed declaration merging for moduleResolution set to bundler (#​701)
  • Removed legacy require (CommonJS) output in piral-core and related libs
  • Improved setup of event listeners in piral-blazor (#​696)
  • Improved fallback signature in piral-translate
  • Improved streaming update in piral-update
  • Updated dependencies
  • Added --strict-port option to the piral-cli debug commands (#​699)
  • Added update capabilities to piral-blazor extension boundaries
  • Added piral-error-overlay to piral-debug-utils
  • Added unhandled-error event fired from the ErrorBoundary

v1.5.6

Compare Source

  • Fixed issue with piral-cli-webpack5 when modifying the config entry point
  • Fixed issue with pre-TypeScript 5 versions with module resolution set to bundler
  • Fixed handling of max event listeners for pilet debug
  • Updated to latest version of dets
  • Added dynamic compiler capability to piral-ng

v1.5.5

Compare Source

  • Fixed piral-ng/extend-webpack for MJS files using not fully specified references
  • Updated TypeScript to use module resolution set to bundler
  • Added piral-ng/standalone to support pure modern Angular standalone (#​690)

v1.5.4

Compare Source

  • Fixed pilet build with --type standalone to end up at feed selection
  • Improved handling of server restart (#​687)
  • Updated piral-cli to also include the .krasrc from the current directory (#​691)
  • Updated piral-blazor to contain support for Piral.Blazor providers
  • Added defineVue3Middleware function to piral-vue3 (#​689)

v1.5.3

Compare Source

  • Fixed handling of Zone.js across different Angular versions
  • Fixed partial appearance of NG04002 for production pilets using piral-ng
  • Fixed lazy loading of defineNgModule in piral-ng/convert to return a generic component
  • Fixed setting of initial values (hard-refresh and load-pilets) via debug.defaultSettings
  • Updated the --feed option for pilet debug to send custom headers
  • Updated piral-breadcrumbs to be independent of React Router (#​681)

v1.5.2

Compare Source

  • Fixed created website emulator paths when running in Windows
  • Fixed website emulator running for pilet debug in Windows
  • Added tea constitution file to repo

v1.5.1

Compare Source

  • Fixed Node.js engine constraint in piral-cli to "16.0.0"
  • Fixed target-specific navigation in piral-blazor
  • Fixed definition of not found page for React Router v6 (#​677)
  • Updated kras to latest v0.16 release
  • Added --type flag to piral publish command

v1.5.0

Compare Source

  • Fixed error when importing once without context (#​664)
  • Fixed issue with monorepos using Rush (#​667)
  • Fixed issue with blocked port in case of full debug reload (#​671)
  • Fixed @Inject with multiple instances in piral-ng (#​673)
  • Fixed standalone pilets depending on @angular/compiler
  • Removed legacy option in piral-cli-webpack5 to support IE8
  • Removed pilet-related options in debug settings when running piral debug (#​670)
  • Improved internal navigation Blazor pilets using piral-blazor
  • Updated dependencies
  • Updated kras to v0.16 to fix some issues and remove request
  • Updated piral publish command to work exclusively for emulator websites
  • Added special entry point to emulator website when accessed online (#​654)
  • Added feed selection view for remote emulator website (#​654)

v1.4.3

Compare Source

  • Fixed issue with piral-blazor using routing in standalone mode
  • Fixed issue with piral-blazor connecting the Piral events
  • Fixed support of piral-blazor for .NET 8 Blazor

v1.4.2

Compare Source

  • Fixed misplaced index.d.ts in a scaffolded pilet (#​658)
  • Fixed issue where pilet publish could remove the source folder (#​657)
  • Updated toggle in debug utilities to always use life cycle (#​659)

v1.4.1

Compare Source

  • Fixed issue with pilet injector for certain apps in monorepos
  • Added support for middleware functions in piral-fetch (#​645)

v1.4.0

Compare Source

  • Fixed issue when target tarball is part of tarball content in pilet pack (#​642)
  • Fixed issue in piral-translate replacing falsy values with empty string (#​651)
  • Moved piral-jest-utils and piral-ie11polyfills-utils into a separate repository
  • Updated documentation on piral-ng (#​646)
  • Updated dependencies (#​641)
  • Updated piral-cli compatibility with Bun as runtime
  • Updated generated code to fully use ES2020
  • Updated to latest version of dets
  • Added support for nested translations in piral-translate (#​648)
  • Added support for Angular 17 in piral-ng
  • Added possibility to publish emulator as a website (#​644)
  • Added support for micro frontends based on module federation (#​643)
  • Added isolation mode option in piral.json to opt-in for piral-component boundary
  • Added option to specify runtime execution path for bundler plugins

v1.3.3

Compare Source

  • Fixed inlined source maps for CSS files of Angular components
  • Fixed import in piral-core prevent piral-cli-vite to properly build
  • Updated direct usage of tslib in piral-base
  • Updated to latest version of dets
  • Added implementation for the FallbackComponent attribute in piral-blazor

v1.3.2

Compare Source

  • Fixed issue with loading order for global Blazor pilets in piral-blazor
  • Added once as a convenience method to EventEmitter
  • Added bun as potential package manager
  • Added bun as bundler option

v1.3.1

Compare Source

  • Updated behavior with unresolved inherited dependencies (#​633)
  • Updated behavior to only update installed dependencies on pilet upgrade
  • Added check to prevent installing of invalid versions locally (#​635)

v1.3.0

Compare Source

  • Fixed issue with global installation in pnpm (#​624)
  • Fixed issue with v.x notation in semver comparisons
  • Fixed inclusion of directory entries in the pilet tarballs (#​629)
  • Updated piral-ng/common to use Angular-version specific package piral-ng-common
  • Added support for features of v9 of Piral.Blazor in piral-blazor (#​626)
  • Added piral-content custom element for rendering arbitrary children in foreign elements
  • Added configuration for default behavior of implicitly defined shared dependency version constraints (#​625)

v1.2.0

Compare Source

  • Fixed issue with loader-utils version
  • Fixed issue with potential URL flickering using piral-ng
  • Fixed build issue in codegen of piral-core on Windows (#​619)
  • Updated importmap with exclude key allowing exclusions
  • Added support for dependencySymbols in piral-blazor
  • Added option to stop module teardown via flags parameter in piral-ng
  • Added abort signal to piral-fetch options (#​621)

v1.1.0

Compare Source

  • Fixed retrieval of dep versions not exporting their package.json
  • Fixed calling custom Webpack config throwing an exception
  • Fixed absolute to a relative path for shared dependencies
  • Updated dependencies of piral-cli-webpack5
  • Added support for optionally centrally shared dependencies
  • Added possibility to extend notification types to piral-notifications
  • Added possibility to further extend options w.r.t. menu type in piral-menu
  • Added lint rule for detecting potential CSS conflicts in pilets (#​611)

v1.0.2

Compare Source

  • Fixed support for piral-extension inside shadow DOM
  • Fixed issue resulting in duplicated files in packed pilets (#​608)
  • Fixed issue in the public path of pilets with schema v1 using piral-cli-webpack5

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (rebase) September 30, 2024 05:48
@renovate renovate bot force-pushed the renovate/piral-cli-webpack5-1.x branch from a53b536 to f181f91 Compare October 18, 2024 05:54
@renovate renovate bot changed the title chore(deps): update dependency piral-cli-webpack5 to v1.6.2 chore(deps): update dependency piral-cli-webpack5 to v1.7.0 Oct 18, 2024
@renovate renovate bot force-pushed the renovate/piral-cli-webpack5-1.x branch from f181f91 to 5904cb9 Compare November 2, 2024 05:44
@renovate renovate bot changed the title chore(deps): update dependency piral-cli-webpack5 to v1.7.0 chore(deps): update dependency piral-cli-webpack5 to v1.7.1 Nov 2, 2024
auto-merge was automatically disabled November 4, 2024 19:06

Pull request was closed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant