question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Build Modernization

See original GitHub issue

https://github.com/mdx-js/mdx/pull/1269 introduces microbundle to handle the preact package builds and enables node v14 native esm usage for mdx (that is, importing mdx from .mjs files). The usage should expand and result in the removal of @pkgr/rollup.

This issue should be closed after the work in #1269 is expanded to the other packages.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
ChristopherBiscardicommented, Dec 26, 2020

I replaced pkgr with microbundle for vue and react already: e7e9d46. It’s no longer used.

great! seems like this would’ve been a useful issue to mention in that PR.

MDX is already built using rollup.

Not all of it is: mdx-js/mdx, mdx-js/loader , and mdx-js/vue-loader use CJS.

you are correct in stating that the packages that don’t get built, are also not built with rollup. I will be more clear about that next time.

I was wondering if this issue was also about changing them to MJS?

This issue is about removing pkgr. If pkgr is gone, we can close this issue.

1reaction
ChristopherBiscardicommented, Dec 22, 2020

To clarify the core purpose of this issue: we are currently on an unsupported one-off build toolchain that isn’t used anywhere else afaict, was last released months ago, and has only 257 weekly downloads: https://www.npmjs.com/package/@pkgr/rollup. It is a project risk issue to depend on a niche build pipeline that we don’t control and isn’t maintained. The work was started to get rid of that toolchain and put us onto something more mainstream that is actively maintained (microbundle in this case) that is still based on rollup.

Your concerns about the handling of esm conversion in micromark are heard, but not required for this conversion as the source code is not changing and all existing exports are being maintained as-is. I’ll repeat that we are not changing the underlying build system like micromark did (from browserify to rollup). MDX is already built using rollup.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Build and modernize faster - IBM
Build and modernize faster. Provide the skills and tools your team needs to drive innovation and move your business forward. Select a challenge...
Read more >
How to build a modernization strategy - Cortex
In the post below, we offer a set of best practices we've collected and some supporting guidelines for your team as you develop...
Read more >
Modernization: Building a modernization project team - Red Hat
In this article, I discuss a proposal to build a success-primed team to modernize a portfolio of applications.
Read more >
Build a Modernization Factory - vFunction
The App Modernization Hub. Modernize more applications across your organization; Track and manage the modernization process with powerful dashboards ...
Read more >
How to Build a Roadmap to App Modernization - The New Stack
Before you start moving everything to the cloud, you need to consider who, when, what and, especially, why. Here's how to start making...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found