-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RSPack support and compatibility #55
Comments
By the fact that there's no alternative in the ecosystem I mean no alternative which is able to preload assets (CSS, scripts, fonts, etc.) |
Hello @KrzysztofZawisla, thanks for the feature request! |
can you please create a repo with reproducible issue. I'll see whether the problem is difficult. Perhaps this is not such complex and I can quickly fix it. |
I think RSPack will need to catch up on webpack features and internal hooks. I doubt there is anything Rspack chokes on this simple config: // 1. create `./src/index.html` with an empty, but valid, HTML5 document
// 2. create `./webpack.config.js`
// 3. run `npx -y @rspack/cli --config webpack.config.js`
const HtmlBundlerPlugin = require('html-bundler-webpack-plugin');
const config = {
mode: "development",
entry: {
index: './src/index.html'
},
plugins: [
new HtmlBundlerPlugin()
]
};
module.exports = config; The error I get is:
But even if you remove |
Hello. I'm also trying to switch to RSPack and have the same problem with the plugin. I would like to see support in the near future. Essentially he is complaining about pug-plugin joining the RSPack ecosystem. Thank you. P.S. - I'm trying to do it myself for pug-plugin. |
@KrzysztofZawisla, @davidmurdoch, @exocornet Currently, RSPack Using the
This is a BUG on the Here is the minimal usage example rspack-html-bundler. rspack.config.js const path = require('path');
const HtmlBundlerPlugin = require('html-bundler-webpack-plugin');
module.exports = {
output: {
path: path.join(__dirname, 'dist/'),
publicPath: '',
},
entry: {},
plugins: [
// TODO: fix rspack issue
new HtmlBundlerPlugin({
entry: {
index: './src/template.html',
},
}),
],
}; How to reproduce
Please, can you create an issue by the
|
Hello, Rspack 1.0 has been released! Can you try to add his support again?) |
Hi @elseify, Rspack 1.0 is not yet compatible with Rspack implements "~10%" of the core (mandatory) features of Webpack, so it is not possible to make this powerful Webpack plugin compatible with Rspack. In fact, Rspack lacks important Webpack features. I checked the new version and saw many missing features that the plugin uses.
|
I understand, it's sad of course. Webpack has become too slow |
This comment was marked as outdated.
This comment was marked as outdated.
@webdiscus any updates on the issue? |
It is not the issue of this plugin. It is the Webpack is best of the best bundler/compiler with rich functionality covered 100% of all possible requirements for web development. No Vite or Rspack or Turbo can do what Webpack can. Yes, Webpack is much slower than Rspack, but Rspack has much less functionality.
I'm sorry. |
Feature request
What is motivation or use case for adding/changing the behavior?
Would be nice to add compatibility with rspack ecosystem as many other webpack plugins are already compatible with rspack. In my project, it's the only plugin that is incompatible with rspack and doesn't have any other equivalent
Useful links: https://www.rspack.dev/
Describe the solution you'd like
Resolve the error on the attached screenshot
Describe alternatives you've considered
None
The text was updated successfully, but these errors were encountered: