-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Describe the bug
Dev server does not run.
To Reproduce
Steps to reproduce the behavior:
Mac [12:32 requestbin$] npm i @particular./micro-requestbin
added 20 packages, and audited 21 packages in 3s
found 0 vulnerabilities
Mac [12:34 requestbin$] yarn install
➤ YN0070: Migrating from Yarn 1; automatically enabling the compatibility node-modules linker 👍
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 3s 177ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ statuses@npm:1.5.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ tr46@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ unpipe@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ webidl-conversions@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ whatwg-url@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0000: └ Completed in 1s 749ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 223ms
➤ YN0000: Done in 5s 163ms
Mac [12:34 requestbin$] yarn dev
Usage Error: Couldn't find a script named "dev".
$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] <scriptName> ...
Mac [12:34 requestbin$]
Expected behavior
When I run yarn dev I expected a server to start running, and it to print out the local endpoint which I can send requests to.
Desktop (please complete the following information):
- MacOS
- 1.0.0
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels