Charles
Charles
The first option should work in both (`@import 'font-awesome';`). The later should as well but currently doesn't for the default builder. A fix for that will require some additional investigation.
The defect here is with the Webpack-based build system. The following should work with the Webpack-based build system but does not: ``` $fa-font-path: 'font-awesome/fonts'; @import 'font-awesome/scss/font-awesome'; ``` The Webpack-based build...
> I'm not sure where it's documented that @import 'font-awesome' is the preferred option, nor am I sure how that would feasibly work. When dealing with JS files, that works...
`font-awesome` does have a `style` entry field which is why it works as a bare specifier: https://github.com/FortAwesome/Font-Awesome/blob/afecf2af5d897b763e5e8e28d46aad2f710ccad6/js-packages/%40fortawesome/fontawesome-free/package.json#L53
It is easy to miss a top-level field in a package.json. The newer `exports` field does make it much more convenient to discover what's available from within package.
Thank you for the contribution. It appears that Yarn PnP has an API available (https://yarnpkg.com/advanced/pnpapi). Would you be interested in converting this PR to use that?
A prime option for this use case would be to use import attributes which provides a standards based solution to the problem. An example for this particular case would be:...
That is one specific (and common) use case involving the need for TypeScript to provide additional syntax to allow import attribute aware type definitions. A standards based approach is strongly...
> To be clear, at least as far as I can tell, our use case requires deployUrl and is incompatible with baseHref. This really seems to be a blocker for...
While the HTML base HREF does affect most relative requests it does not affect all. However, while ctrl+click behavior with relative links may be a concern for some applications, some...