This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release, this PR will be updated.
Releases
meteor-vite@1.10.0
Minor Changes
60491ff6: Add support for externalizing imports for npm packages bundled with Meteor
Allows you to point Vite to the Meteor bundle for some or all imports of an npm package.
In most cases, you don't need to use this feature, but if you're using Meteor packages that
have peer npm-dependencies, you can avoid the dependency being included twice in your final
production bundle by hinting to Vite that this npm dependency is provided by Meteor.
import React from "react"; // This will import from your node_modules
// If you have a Meteor package that depends on React, then React will already be
// in your Meteor client bundle. So you can instruct Vite to not import from node_modules
import React from "meteor:react"; // This will import from your Meteor bundle
Fixes #33
vite-bundler@1.12.9
Patch Changes
b6871542: Keep npm import references when analyzing Meteor client dependencies
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release, this PR will be updated.
Releases
meteor-vite@1.10.0
Minor Changes
60491ff6: Add support for externalizing imports for npm packages bundled with Meteor
vite-bundler@1.12.9
Patch Changes