Roman

Agree with @CharlesStover here. Would be great to have a mock/stub implementation of the RUM library. Not only for SSR purposes but also for testability. A great example of this...

Should this be a `withX` helper method you think?

Having the same issue. Bundle size is huge. Using with Nuxt: ``` [ 'nuxt-fontawesome', { imports: [ { set: '@fortawesome/free-solid-svg-icons', icons: [ 'faLevelUpAlt', 'faSearchMinus', 'faSearchPlus', 'faSearch', 'faChevronRight', 'faChevronDown', 'faCompressArrowsAlt', 'faExpandArrowsAlt'...

What I actually did was get rid of `nuxt-fontawesome` completely. And I am using `@fortawesome/vue-fontawesome` component directly. ``` import { FontAwesomeIcon } from '@fortawesome/vue-fontawesome' import { faSearchPlus, faSearchMinus, faSearch }...

IMO package type shall not have a direct relation with the output format. Because many tools (esp. esbuild-based ones, such as tsup) can transpile (CJS, ESM) => (CJS, ESM).

However, the biggest problem I ran into when trying to make an ESM-compatible package, is the fact that all imports now must be imported with a `.js` extension. ```ts import...

And then because projen itself is not ESM, you actually cannot import it into an ESM package. The only way to make a projen-based ESM package that I found was...

One awesome tool that helped to figure out the ESM/CJS exports mess was this one: https://github.com/arethetypeswrong/arethetypeswrong.github.io It's comprehensive and is made by one of the core TS project members. It's...

> you’ll get an ESM projen project. I wish!! 😁 ``` 👾 postinstall » pre-compile » save-schema | ts-node scripts/saveSchema.ts TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /users/foo/tms-apollo-graphql-app/scripts/saveSchema.ts at new...

This was on Node `v20.7.0`