Make `['style']` resolve condition optional in vite-plugin-angular

[mrginglymus]

Please provide the environment you discovered this bug in.

#141

Which area/package is the issue in?

vite-plugin-angular

Description

#141 added the custom condition style to resolve.condition with no way to override:

analog/packages/vite-plugin-angular/src/lib/utils/plugin-config.ts

Lines 140 to 142 in cff12cd

	resolve: {
	conditions: ['style'],
	},

However, I have a package.json that contains export definitions like this:

 "./stylesheets/*": {
      "style": "./dist/*/stylesheet.css",
      "types": "./dist/*/stylesheet.d.ts",
      "default": "./dist/*/stylesheet.js"
    },

As I'm using css modules, I want the js import when importing from js, which #141 prevents.

Please provide the exception or error you saw

Other information

No response

I would be willing to submit a PR to fix this issue

• Yes
• No

[mrginglymus]

For now I have another plugin that removes the style condition from the analog plugins.

[brandonroberts]

Thanks for the detailed report — and for sharing your workaround.

The style resolve condition was added in #141 specifically so libraries like Angular Material resolve their .css style entry points. Your case is the inverse: a package whose exports map lists style ahead of the entry you actually want (the JS/CSS-modules entry). Since Vite/Node activate style and pick the first matching condition present in the exports object, it wins over default.

Rather than adding a dedicated plugin option for this edge case, the recommended approach is the kind of userland plugin you're already using. Mutating the resolved config in configResolved (with enforce: 'post') is the most reliable way, since the condition is injected during Analog's config hook:

import type { Plugin } from 'vite';

function removeStyleResolveCondition(): Plugin {
  return {
    name: 'remove-style-resolve-condition',
    enforce: 'post',
    configResolved(config) {
      const conditions = config.resolve.conditions;
      const index = conditions.indexOf('style');
      if (index !== -1) {
        conditions.splice(index, 1);
      }
    },
  };
}

// vite.config.ts
export default defineConfig({
  plugins: [angular(), removeStyleResolveCondition()],
});

Note that removing the condition will affect Angular Material style resolution if you're using it in the same app.

---

Generated by Claude Code

[mrginglymus]

Hi @brandonroberts and or @claude - I don't think it's good design to include a hard-coded workaround for behaviours in a third party library in a plugin like this. It should be the final users responsibility to add in the style to their vite conditions if they need it, rather than for this library to support a common but far from universal use case.

[brandonroberts]

@mrginglymus maybe we can revisit this for Analog 3.0 as it only applies with Angular Material.