`@11ty/font-awesome` doesn't seem to work with EJS

Aperta
  • Qualcosa non va?
#305 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Ferma
Ambito
frontend

Direzione di ricerca

The issue names the 11ty-migration branch and /community as the reproduction entry point; start by visiting a page with Font Awesome icons and comparing the EJS template with the @11ty/font-awesome documentation. Done means the project has a supported way to include the bundle for EJS and the icons render on /community.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Thanks in advance for your bug report!
  • Have you reproduced this issue in incognito/private browsing?
  • Have you made sure you issue doesn't already exist?
Where is the URL that this occurs?

(pertaining to the 11ty-migration branch)

What's your issue?

Unless I'm misunderstanding something, I can't get @11ty/font-awesome to work because it requires features that aren't implemented in EJS.

The docs explain that you need to include this somewhere on any page where you use icons:

{% getBundle "fontawesome" %}

Of course, that's a Liquid template snippet. The getBundle shortcode doesn't seem to be available in EJS, nor does any other shortcode. I don't see an easy way of including them in an EJS template.

It feels like we're using Eleventy in hard mode just because we've chosen EJS. If there's a particular reason we're using EJS instead of Liquid or Nunjucks or something, that's fine, but otherwise I'd be in favor of moving to one of those templating languages instead so I don't have to reimplement so much stuff.

Which OS/Browser/Version does this happen on?

All.

Steps to Reproduce/Additional Details:

Visit any page that uses FA icons (like /community).

Lingua principale
EJS
Stelle
31
Fork
33
Merge medio
2m
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pulsar-edit/pulsar-edit.github.io

Tutte le issue di pulsar-edit/pulsar-edit.github.io

Issue simili

Altre issue su Web Dev

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.