Consider restricting the plugin to particular files via options.include

[hubeishuaige]

use rollup-plugin-inject ，tip： rollup-plugin-inject: failed to parse xxxxx Consider restricting the plugin to particular files via options.include

Although it does not affect my project permission, I am still very unhappy to see it

[jordanade]

Same problem here. It seems to be triggered by an sass import from node_modules in my case:
@import "~bootstrap-sass/assets/stylesheets/bootstrap";

[potatohoney-p]

For the CSS/Sass case, restrict inject to the JavaScript files that actually need injected globals, while keeping your existing injection mappings:

inject({
  include: ["**/*.js", "**/*.mjs", "**/*.cjs"],
  // Keep your existing mappings here, for example:
  $: "jquery",
})

The warning comes from inject trying to parse a matching file as JavaScript. In @rollup/plugin-inject@5.0.5, the transform first checks the file filter and then searches for configured identifiers; if one occurs in a stylesheet, it can reach the JS parser and emit this warning. The stylesheet still needs its normal CSS/Sass plugin. The filter only prevents inject from handling it.

Verified with Rollup 4.53.3 and inject 5.0.5 using a CSS fixture containing $, a JS entry using $, and a separate CSS-to-JS transform: without include, the CSS produced PARSE_ERROR; with the filter above, there were zero warnings and the JS injection was still present in the bundle. This is a minimal reproduction of the stylesheet warning, not a test of the full original project.

If your injection targets include TypeScript or JSX, adjust the include patterns for those files and make sure their syntax has been transformed into JavaScript before inject parses them. Do not include CSS/Sass just to make the warning disappear, and do not suppress every parse warning: a warning on an actual JS target deserves a separate check.