LivelyKernel / LivelyKernel/lively.next

Caching libraries

Open
#1,761 1 comment 0 reactions 0 assignees View on GitHub
✨ enhancement
Dominant language
JavaScript
Stars
90
Forks
20
PR merge metrics
No merged PRs in 30d

Description

**Describe the Feature**
Freezing has been failing for me this afternoon because
```
TypeError: Could not load https://jspm.dev/npm:immutable@4.0.0-rc.12!cjs: fetch failed
```
Twice it was due to a Connect Timeout Error, and once due to a SocketError: other side closed.

Presumably due to some outage at jspm.dev, or jspm.dev got too budy, or...I will try again later.
But it did make me wonder why the freezer doesn't download the node_modules (as node applications do) and use the cached version of the library rather than fetching on every build.

**Graphics**
If applicable, provide screenshots/videos of similar ideas in other software.

**Implementation Details**
If applicable, provide insights with regards to implementing this feature that you already have.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the freezer's current fetch of libraries from jspm.dev and how dependencies are handled during builds. The work is done when the freezer can reuse a locally cached node_modules library on later builds instead of fetching it every time, including when jspm.dev is unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.