expo / expo/snack

Unable to resolve dependency of newly added Packages

Open
#387 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
508
Forks
178
Avg merge
5h 7m
Merged PRs (30d)
5

Description

### Summary

This issue has been around for a long time now, I cannot understand why no fix has been added untill now?

This issue is triggered when adding new packages to `npm` and try installing it on `snack.expo`

Now you may say that the packages is not regstered yet, I am able to install the package with `visual code` command line `npm install`

This issue dose not always happen. Sometime the package gets found sometime it dose not.

### What platform(s) does this occur on?

Android, iOS, Web

### SDK Version

47

### Reproducible demo or steps to reproduce from a blank project

create new Package and add it to `npm` then added to `snack.expo`.

Obs found some issue with the package, fixed it and publish a new version to `npm`

Add it to `snack.expo` and there you will see the issue

Contributor guide

Open the contributing guide

Research direction

No source file, test, package name, or entry point is identified. Start by reproducing the installation in snack.expo with a newly published npm package on Android, iOS, and Web; done means the dependency resolves reliably after publishing an updated package.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.