Rollup

@RollupJS

The next-generation JavaScript module bundler.

node_modules
rollupjs.org
Joined September 2016
6 Photos and videos Photos and videos

Tweets

You blocked @RollupJS

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @RollupJS

  1. Retweeted
    Aug 13

    🎁 As of v2.15.0, lots of cool stuff has happened at since I last tweeted! The biggest focus was interop: - "auto" is finally compatible with how most others are doing it - "esModule"/"default"/"defaultOnly" get rid of interop helpers (cont.)

    1 reply 16 retweets 57 likes
    Show this thread
    Show this thread
    Undo
  2. Retweeted
    Aug 13

    📣 Plugin Release Day 🎉 🍣 node-resolve v9.0.0 🍣 pluginutils v4.0.0 🍣 babel v5.2.0 🍣 commonjs v15.0.0 🍣 dynamic-import-vars v1.1.0 🍣 multi-entry v4.0.0

    2 retweets 15 likes
    Undo
  3. Retweeted
    Jul 13

    Is it ok if v3 will only generate ES6 compatible code, but we add a guide how to use Babel as a post-processing step to get ES5 output? Or do you insist that we add an option to get the old ES5 compatible code (a lot of overhead for us resulting in slower development)?

    9 replies 7 retweets 19 likes
    Show this thread
    Show this thread
    Undo
  4. Retweeted
    Jun 21

    Again, lots of new stuff in the world🎉: As of v2.18.0, inlineDynamicImports, manualChunks and preserveModules can now be applied per output, making it much faster if you want bundles with and without those options! (cont.)

    3 replies 6 retweets 62 likes
    Show this thread
    Show this thread
    Undo
  5. Retweeted
    Jun 7

    I know many of you have other things on their minds right now that are definitely more important. Still a lot has happened at since I last tweeted (which was 5(!) minor versions ago), here some bits (cont.):

    1 reply 8 retweets 51 likes
    Show this thread
    Show this thread
    Undo
  6. Retweeted
    May 10

    And last, rebuild debounce delay can now be configured–and we set it to 0 as a default for instant rebuilds: See also for the release notes

    1 reply 1 retweet 4 likes
    Show this thread
    Show this thread
    Undo
  7. Retweeted
    May 10

    This is nice as of itself, but you now also get access to this information when creating manual chunks, allowing you to do some badass optimizations: (scroll down for the advanced example)

    1 reply 2 retweets 4 likes
    Show this thread
    Show this thread
    Undo
  8. Retweeted
    May 10

    If you do module graph analysis in a plugin, now you not only get the dependencies but also the dependent modules for each module:

    1 reply 1 retweet 3 likes
    Show this thread
    Show this thread
    Undo
  9. Retweeted
    May 10

    Finally, we added nullish coalescing in v2.9.0–with full tree-shaking support: Now let's keep fingers crossed as optional chaining is still waiting on upstream…

    2 replies 9 retweets 54 likes
    Show this thread
    Show this thread
    Undo
  10. Retweeted
    May 5

    If you code-splitting, this is for you: v2.8.0 will finally get rid of additional facade chunks for dynamic imports 🎉 Try it out!

    1 reply 20 retweets 91 likes
    Show this thread
    Show this thread
    Undo
  11. Retweeted
    Mar 29

    And last, I refactored the CLI watch module and fixed some issues. Did you know that Rollup CLI also watches your config file for changes and reloads it when necessary? Now this will even work if the initial version throw an Error.

    1 reply 3 retweets 15 likes
    Show this thread
    Show this thread
    Undo
  12. Retweeted
    Mar 29

    And more stuff that was not properly documented: Did you know Rollup supports configs from npm via `rollup -c node:my-config-name`? (cont.)

    1 reply 1 retweet 6 likes
    Show this thread
    Show this thread
    Undo
  13. Retweeted
    Mar 29

    Also by popular request, you can now use the config loader from Rollup CLI via `const loadConfigFile = require('rollup/dist/loadConfigFile')` (cont.)

    1 reply 1 retweet 3 likes
    Show this thread
    Show this thread
    Undo
  14. Retweeted
    Mar 29

    We keep extending Node 13+ native ESM support in with v2.3.0: - use unprocessed ESM configs in Node 13 via the .mjs extension, i.e. rollup.config.mjs - use unprocessed CJS configs in all Node versions via the .cjs extension (cont.)

    1 reply 6 retweets 44 likes
    Show this thread
    Show this thread
    Undo
  15. Retweeted
    Mar 26

    Also, you can now query the entire module graph including dynamic imports via `this.getModuleInfo`:

    2 replies 1 retweet 8 likes
    Show this thread
    Show this thread
    Undo
  16. Retweeted
    Mar 26

    A cool hook we added in v2.2.0: renderDynamicImport allows you to completely control how dynamic import expressions are rendered for all formats Use it to e.g. retain dynamic imports in Node 13 CommonJS, but the sky is the limit

    2 replies 8 retweets 49 likes
    Show this thread
    Show this thread
    Undo
  17. Mar 6

    And that's mostly it, folks, hope you like it. See the full release notes with all changes here:

    1 reply 2 retweets 23 likes
    Show this thread
    Show this thread
    Undo
  18. Mar 6

    For all those out there who are rebundling : Rollup is now shipping ES2018 code and has also been restructured via code-splitting so that watch mode and CLI are nicely separate but reuse shared code so you only pull in what you really need (cont.)

    2 replies 3 retweets 21 likes
    Show this thread
    Show this thread
    Undo
  19. Mar 6

    For those living in the future: Rollup can now be imported in Node as an ES-Module–without a bundler: (cont.)

    1 reply 2 retweets 19 likes
    Show this thread
    Show this thread
    Undo
  20. Mar 6

    This is really the hidden gem here if you do code-splitting: Rollup now uses side-effect detection to not only avoid unnecessary empty imports, it will also create much better chunks. Check out the examples here: (cont.)

    1 reply 2 retweets 25 likes
    Show this thread
    Show this thread
    Undo

@RollupJS hasn't Tweeted yet.

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·