vsivsi/meteor-job-collection

Support dynamic import

Open

#259 opened on Oct 12, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)CoffeeScript (389 stars) (68 forks)batch import
enhancementhelp wanted

Description

First of all, this is a great package and it has shorten my development by a lot as I move a lot of long running tasks in the background like sending SMS or uploading to S3.

But if there is one part that we can improve, it is with dynamically importing this package in the client. In my case, less than 5% of my users actions use background jobs but it is the 5th biggest resource being downloaded.

Is there a possibility to setup the package for dynamic import as supported by Meteor since 1.5?

https://github.com/meteor/meteor/issues/8745

Contributor guide

Tech stack
javascript
Domain
backendfull stack
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of Meteor's dynamic import systemFamiliarity with package development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
This feature request asks for dynamic import support as provided by Meteor since version 1.5. The linked issue (meteor/meteor#8745) should be reviewed to understand the dynamic import mechanism. The current package likely loads all modules upfront; implementing dynamic imports would require modifying the package to use Meteor's import() function for lazy loading. Key files to investigate include the main entry point and any modules that are conditionally used.