-
Notifications
You must be signed in to change notification settings - Fork 8
Hacked node-speaker exports and other imports here to get examples working #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 1 commit
74538a7
2e32033
1370e8a
d66d9eb
9ce27fe
acfbea2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
…rking
- Loading branch information
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -61,14 +61,14 @@ | |
| }, | ||
| "dependencies": { | ||
| "@types/node": "^13.13.15", | ||
| "@types/usb": "^1.5.1", | ||
| "@types/usb": "^1.5.2", | ||
mildsunrise marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| "usb": "^1.6.3" | ||
| }, | ||
| "devDependencies": { | ||
| "@types/jest": "^23.3.14", | ||
| "coveralls": "^3.1.0", | ||
| "jest": "^26.4.2", | ||
| "speaker": "^0.5.2", | ||
| "speaker": "https://github.com/cjheath/node-speaker.git", | ||
|
||
| "ts-jest": "^26.2.0", | ||
| "ts-node": "^9.0.0", | ||
| "typedoc": "^0.17.0-3", | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -17,6 +17,7 @@ | |
| "emitDecoratorMetadata": true | ||
| }, | ||
| "include": [ | ||
| "lib" | ||
| "lib", | ||
| "examples" | ||
|
Owner
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. AFAIK that would cause examples to be compiled and distributed with the NPM package... I think examples don't need to be published, just the actual library code
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Right, probably not sensible for a library module. But some instructions on building the examples would be good, also the ability to build them without installing. Guess I don't understand why they import from ".." if there's no code there?
Owner
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. they import from '..' because that's the module itself :) so according to as per running / building examples, you're just supposed to run them with
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Excellent idea :) thanks! |
||
| ] | ||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changing
..to../libshouldn't be necessary to run the examples, as long as you've rannpm run buildfirst and you have compiled files indist🤔Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
btw! these examples are meant to be run with
ts-nodeor similarThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. New to the ecosystem and didn't have any build instructions :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also; opening in vscode is disappointing; that guesses that the build instructions are just to run tsc, so "Start Debugging" doesn't work