meteor-vite@3.9.0-beta.2

Minor Changes

• 7f46f02: Add option to override the internal Vite asset output directory through setting a METEOR_VITE_ASSETS_DIR environment variable when building for production.
• 37d7510: Update peer dependency version requirement for Vite to also support Vite v7
• 4f99214: Added deprecation note to the confusing assetsBaseUrl field in Meteor-Vite's plugin options.
  The field has the same effect as setting a base URI in Vite's official config options.
• 8877164: Add package.json exports for internal utilities and constants. Exports Vite environment keys for the Meteor client and server environments.

Patch Changes

• 5026894: Remove type definition for deprecated chunk filename configuration

jorgenvatle_vite@1.6.0-beta.4

Patch Changes

• 217ba87: Fix issue where starting the Meteor dev server with just 'meteor' would sometimes cause the Meteor-Vite build plugin to be disabled if arguments like '--raw-logs' are passed.

vite-bundler@3.0.1

Patch Changes

• a2f015d: Added deprecation notice for apps running on Meteor v3

meteor-vite@3.9.0-beta.1

Patch Changes

• 4cfcf72: Added type exports for meteor-vite/plugin options.

jorgenvatle_vite@1.6.0-beta.2

Minor Changes

• f0e1fd4: Attempt to unwrap any symlinks in current project root path

  • meteor/meteor#13819
  • #352

meteor-vite@3.9.0-beta.0

Minor Changes

• 2625dbb: Added internal utility for consistently formatting log messages

• ec8a295: Bundle log formatting utility packages into meteor-vite package to prevent warnings from Meteor when those packages aren't a direct dependency of the peer project.

  • Fixes (which wasn't fully resolved) #286

• d133984: Refactor internal meteor-vite directory structure and package.json exports to provide more clear separation of client, server, plugin and internal module exports.

Patch Changes

• cb18b0a: Prevent Meteor from attempting to start the Vite dev server when starting the production server bundle with a non-production NODE_ENV variable.

• 217ed2d: Add warning message when non-ESM Vite configs are detected

  • Fixes #322

• 9db5d7a: Fix issue where apps without a .meteor/finished-upgraders file would cause package export analysis to fail with a file-not-found exception when building for production.

• 13a9429: Add warning message whenever a .meteorignore file is detected in the application root directory.

  • #345

jorgenvatle_vite@1.6.0-beta.0

Minor Changes

• ec8a295: Bundle log formatting utility packages into meteor-vite package to prevent warnings from Meteor when those packages aren't a direct dependency of the peer project.

  • Fixes (which wasn't fully resolved) #286

• d133984: Refactor internal meteor-vite directory structure and package.json exports to provide more clear separation of client, server, plugin and internal module exports.

meteor-vite@3.8.0

Minor Changes

• ce4ef77: Update Atmosphere package parser to handle nested "browser" fields in package.json exports.

  • #344

Patch Changes

• 6bcb86d: Use Vite assets dir as base path instead of full assets URL for Vite asset middleware.

  • Fixes #346

• bdb3d8e: Fix issue where Vite asset base URLs that include a protocol (e.g. https) would result in malformed asset URLs being added to the production app's main HTML file.

  • #345
  • Added one-off notice to Vite asset 404 logger with info on how to debug assets potentially not being included in the Meteor bundle.

• c65bd34: Move redundant VITE_DYNAMIC_ASSET_BASE_URL global definition into production server entry

  • Fixes #340

jorgenvatle_vite@1.5.3

Patch Changes

• 614839c: Check for custom Vite config file paths when preparing client boilerplate. Ref: #341

meteor-vite@3.7.2

Patch Changes

• 614839c: Check for custom Vite config file paths when preparing client boilerplate. Ref: #341