nollup
nollup copied to clipboard
PepsRyuu
Rollup compatible development bundler for fast rebuilds and HMR.
It would be nice if these two options from `webpack-dev-server` were available: https://webpack.js.org/configuration/dev-server/#devserveropen https://webpack.js.org/configuration/dev-server/#devserveropenpage Not a huge priority, but `open: true` to open `http://locahost:port/` would be good enough for me.
In my project I'm using Workbox via [rollup-plugin-workbox-inject](https://www.npmjs.com/package/rollup-plugin-workbox-inject) to compile service worker. My rollup configuration has two rollup input entries: one for app and other for service worker. This doesn't...
Some advantages: This would add support for more ways to configure nollup: - a `nollup` property in `package.json` - a `.nolluprc` file in JSON or YAML format - a `.nolluprc.json`...
Aaaah, I'm too excited about this! I've look at how Webpack Dev Server does it: https://github.com/webpack/webpack-dev-server/blob/master/lib/Server.js#L178. They use a compiler hook and write errors on the WS as 'error' event....
Looks like nollup hasn' been updated in a while, and requires rollup 2 while rollup 3 has been out for quite a while
I wrote my rollup config in module format (hence used `rollup.config.mjs` as the file name). This works perfectly fine for rollup however when using nollup it complaints about the first...
I am building a sub-app and I want to remove the base path before it goes to the `dist` folder building in vite, but configuring using rollup ``` rollupOptions: {...
TODO: * Need to see if this accumulates and prevent it from doing so. Preferably only calling chokidar when new files are added to the module graph.
That's a widespread problem with compability nollup and actual versions of official rollup plugin (@rollup/plugin-node-resolve, @rollup/plugin-commonjs etc), for example with node-resolve v 15.2.3: > Error: Insufficient rollup version: "@rollup/plugin-node-resolve" requires...
