Update babel packages to match major, fix dependency issues #591
No reviewers
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
Osprey
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
resilience
Tom's Wishlist
type: bug
type: discussion
type: error handling
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/spee.ch#591
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "fix-babel-deps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tested with yarn
1.7.0
and npm5.6.0
(included with Node v8.11)I'm not including a yarn.lock (yet) since we aren't using it universally.
LGTM
I noticed that we have both a yarn lockfile and a package-lock file. Are we using yarn or npm? we should remove one.
also servers should be running npm 6.4+ so I would not rely on npm 5.* anymore
@nikooo777 the yarn.lock was added by mistake.
Why aren't the servers on LTS?