Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ES6 modules not working with Symfony Asset-Mapper

Open
  • Is something wrong?
#900 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start by reading related issue #889 and reproducing the ES6 import with Symfony Asset-Mapper. Investigate how jsDelivr resolves @knight-lab/timelinejs and which package files it serves. Done means the import exposes Timeline without the reported export error.

Written by the indexing model from the issue text.

Description

I think this is related to #889

When using
import { Timeline } from '@knight-lab/timelinejs';
the Symfony Asset-Mapper uses jsDelivr to get the correct files.

However jsDelivr can not get the correct files and throws an error.
Therefore we get The requested module '@knight-lab/timelinejs' does not provide an export named 'Timeline'.

I think solving the related issues should solve this situation too.

Thanks for the package, really loving it <3

Dominant language
JavaScript
Stars
3.2k
Forks
644
Avg merge
3m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NUKnightLab/TimelineJS3

All issues in NUKnightLab/TimelineJS3

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.