mike-works / typescript-fundamentals Goto Github PK
View Code? Open in Web Editor NEWMike North's 2018 TypeScript Fundamentals Course
Home Page: https://frontendmasters.com/courses/typescript/
License: BSD 3-Clause "New" or "Revised" License
Mike North's 2018 TypeScript Fundamentals Course
Home Page: https://frontendmasters.com/courses/typescript/
License: BSD 3-Clause "New" or "Revised" License
The instructor mentions at the end of "Dictionary Solution" lesson that it will be available on the repo, but I don't see it there. After contacting support via Intercom, I was directed to leave an issue on the repo. Thanks!
I would imagine it would be this file, but filled in https://github.com/mike-works/typescript-fundamentals/blob/362113346f26fde233919a04a9e8a87f81c8e319/challenges/dict/src/index.ts
Branch | Build failing 🚨 |
---|---|
Dependency | babel-loader |
Current Version | 7.1.4 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
babel-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 3 commits.
f3bfed9
7.1.5
fa91723
Merge pull request #638 from lencioni/7.x-md4
19fb463
Use MD4 instead of SHA1 for filename hashes
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Is your feature request related to a problem? Please describe.
This is related to a bug I ran into! The current challenges rely on a mocha.opts
file to specify mocha flags. However, this method of specifying options has been deprecated, which prevents me from running tests (specified in Additional context section).
Describe the solution you'd like
I was able to create a .mocharc.json
configuration file based on the docs that fixes the issue and allows the tests to run, so it would probably help to replace the mocha.opts
file with that.
challenges/address-book/.mocharc.json
:
{
"require": ["ts-node/register", "source-map-support/register"],
"timeout": 60000,
"extension": ["js", "ts", "json"],
"spec": "test/**/*.test.ts"
}
Describe alternatives you've considered
The mocha version in the package.json could use semver to specify an older version that allows for the mocha.opts file, but replacing the configuration file to keep up with newer mocha versions seems more reasonable.
Additional context
This is the error I initially got when I ran yarn test
in the challenges/address-book
folder:
$ yarn test
yarn run v1.22.5
$ mocha
Error: No test files found
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
I then tried to edit the test
script in the package.json from just "mocha"
to "mocha --opts test/mocha.opts"
because I thought it would work with the older mocha version, but I still got an error:
× ERROR: --opts: configuring Mocha via 'mocha.opts' is DEPRECATED and no longer supported.
Please use a configuration file instead.
error Command failed with exit code 1.
After this I made the configuration file.
[ Mac OS 10.14.1 - MBP 2017] System Information
Describe the bug
Initial run start project would not compile following the error messages i npm installed
extract-text-webpack-plugin and babel loader
My current package.json here -> package.json
Then:
In autocomplete-sfc lesson in app.tsx the super() call has red squiggle underline as the error location
passing an object into super seems to fix the issue.
super({});
And had to pass ?: to each item in the interface PlaceDetails to get render:
Expected behavior
Expected initial compile to compile/render to start the lesson with instructor.
Additional context (optional)
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial
branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.
I was watching this episode: https://frontendmasters.com/courses/typescript/integrating-react-typescript and tried to follow along, but I couldn't find this folder and npm start _first
response is:
Unknown exercise: _first! Valid exercises are:
accounts
autocomplete-2
autocomplete-3
autocomplete-4
autocomplete-sfc
cashier
color-functions
dealer
fib
stack
Branch | Build failing 🚨 |
---|---|
Dependency |
react
|
Current Version | 16.3.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
React.unstable_Profiler
component for measuring performance. (@bvaughn in #12745)getDerivedStateFromProps()
regardless of the reason for re-rendering. (@acdlite in #12600 and #12802)forwardRef()
on a deeper setState()
. (@gaearon in #12690)propTypes
on a context provider component. (@nicolevy in #12658)react-lifecycles-compat
in <StrictMode>
. (@bvaughn in #12644)forwardRef()
render function has propTypes
or defaultProps
. (@bvaughn in #12644)forwardRef()
and context consumers are displayed in the component stack. (@sophiebits in #12777)getDerivedStateFromProps()
support to match the new React DOM behavior. (@koba04 in #12676)testInstance.parent
crash when the parent is a fragment or another special node. (@gaearon in #12813)forwardRef()
components are now discoverable by the test renderer traversal methods. (@gaearon in #12725)setState()
updaters that return null
or undefined
. (@koba04 in #12756)There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | tslint-microsoft-contrib |
Current Version | 5.0.3 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
tslint-microsoft-contrib is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
System Information
Describe the bug
Unable to run yarn start .
To Reproduce
Steps to reproduce the behavior:
yarn global add typescript tslint ts-node
yarn
yarn start autocomplete-sfc
Error: Chunk.entrypoints: Use Chunks.groupsIterable and filter by instanceof Entrypoint instead
at Chunk.get (/Users//Dropbox/Development/tscriptFEM/node_modules/webpack/lib/Chunk.js:846:9)
at /Users/scarter1/Dropbox/Development/tscriptFEM/node_modules/extract-text-webpack-plugin/dist/index.js:176:48
at Array.forEach ()
at /Users/scarter1/Dropbox/Development/tscriptFEM/node_modules/extract-text-webpack-plugin/dist/index.js:171:18
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users//Dropbox/Development/tscriptFEM/node_modules/tapable/lib/HookCodeFactory.js:32:10), :7:1)
at AsyncSeriesHook.lazyCompileHook (/Users//Dropbox/Development/tscriptFEM/node_modules/tapable/lib/Hook.js:154:20)
at Compilation.seal (/Users//Dropbox/Development/tscriptFEM/node_modules/webpack/lib/Compilation.js:1242:27)
at hooks.make.callAsync.err (/Users//Dropbox/Development/tscriptFEM/node_modules/webpack/lib/Compiler.js:546:17)
at _err0 (eval at create (/Users//Dropbox/Development/tscriptFEM/node_modules/tapable/lib/HookCodeFactory.js:32:10), :11:1)
at _addModuleChain (/Users//Dropbox/Development/tscriptFEM/node_modules/webpack/lib/Compilation.js:1093:12)
at processModuleDependencies.err (/Users//Dropbox/Development/tscriptFEM/node_modules/webpack/lib/Compilation.js:1005:9)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9
In the v2 branch, notes, 6-guard-and-extreme-types, line 32:
28 * (3) When to use `unknown`
29 * Unknowns are good for "private" values that we don't want to expose through a public API.
30 * They can still hold any value, we just must narrow the type before we're able to use it.
31 *
32 * We'll do htis with a type guard.
33 */
I suppose that it should be "We'll do this with a type guard."
System Information
Describe the bug
yarn test throwing below error in windows because of scripty:
internal/child_process.js:323 throw errnoException(err, 'spawn');
^
Error: spawn UNKNOWN
at _errnoException (util.js:992:11)
at ChildProcess.spawn (internal/child_process.js:323:11)
at exports.spawn (child_process.js:502:9)
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.
Since we did not receive a CI status on the greenkeeper/initial
branch, we assume that you still need to configure it.
If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/
.
We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
Branch | Build failing 🚨 |
---|---|
Dependency |
react-test-renderer
|
Current Version | 16.3.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
react-test-renderer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
React.unstable_Profiler
component for measuring performance. (@bvaughn in #12745)getDerivedStateFromProps()
regardless of the reason for re-rendering. (@acdlite in #12600 and #12802)forwardRef()
on a deeper setState()
. (@gaearon in #12690)propTypes
on a context provider component. (@nicolevy in #12658)react-lifecycles-compat
in <StrictMode>
. (@bvaughn in #12644)forwardRef()
render function has propTypes
or defaultProps
. (@bvaughn in #12644)forwardRef()
and context consumers are displayed in the component stack. (@sophiebits in #12777)getDerivedStateFromProps()
support to match the new React DOM behavior. (@koba04 in #12676)testInstance.parent
crash when the parent is a fragment or another special node. (@gaearon in #12813)forwardRef()
components are now discoverable by the test renderer traversal methods. (@gaearon in #12725)setState()
updaters that return null
or undefined
. (@koba04 in #12756)There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Executing "C:\aaasukumar\typescript\tscript\scripts\test\index.sh":
#!/bin/bash
./node_modules/.bin/jest --no-cache --watch $2
internal/child_process.js:323
throw errnoException(err, 'spawn');
^
Error: spawn UNKNOWN
at _errnoException (util.js:1024:11)
at ChildProcess.spawn (internal/child_process.js:323:11)
at exports.spawn (child_process.js:502:9)
at module.exports (C:\aaasukumar\typescript\tscript\node_modules\scripty\lib \run\spawn-script.js:8:15)
at C:\aaasukumar\typescript\tscript\node_modules\scripty\lib\run\commandify. js:6:7
at C:\aaasukumar\typescript\tscript\node_modules\scripty\node_modules\async\ lib\async.js:718:13
at iterate (C:\aaasukumar\typescript\tscript\node_modules\scripty\node_modul es\async\lib\async.js:262:13)
at async.forEachOfSeries.async.eachOfSeries (C:\aaasukumar\typescript\tscrip t\node_modules\scripty\node_modules\async\lib\async.js:281:9)
at parallel (C:\aaasukumar\typescript\tscript\node_modules\scripty\node_mod ules\async\lib\async.js:717:9)
at async.series (C:\aaasukumar\typescript\tscript\node_modules\scripty\node modules\async\lib\async.js:739:9)
npm ERR! Test failed. See above for more details.
Branch | Build failing 🚨 |
---|---|
Dependency | @types/react-test-renderer |
Current Version | 16.0.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@types/react-test-renderer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Is your feature request related to a problem? Please describe.
If I'm not mistaken, the Basics code example under "Intersection types" actually shows a union type and vice versa.
Cf. https://www.typescriptlang.org/docs/handbook/advanced-types.html
Describe the solution you'd like
The headings could be swapped.
Thank you for this great course.
Branch | Build failing 🚨 |
---|---|
Dependency | webpack-hot-middleware |
Current Version | 2.22.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
webpack-hot-middleware is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 4 commits.
c85789a
2.22.3
84c3f54
Merge pull request #322 from cainrus/support_http2
22e922b
Support HTTP/2
8d46df6
Add issue templates
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency |
@types/react-dom
|
Current Version | 16.0.5 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@types/react-dom is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | tsutils |
Current Version | 2.18.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
tsutils is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Features:
WrappedAst
interface that models the type of a wrapped SourceFile more accurategetWrappedNodeAtPosition
utiltiy that takes a NodeWrap
and returns the most deeply nested NodeWrap that contains the given positionThe new version differs by 3 commits.
a167d61
v2.19.0
76ef784
Add getWrappedNodeAtPosition utility
02b1427
Introduce WrappedAst iterface to correctly model type of wrapped SourceFile
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | node-sass |
Current Version | 4.9.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
node-sass is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
--source-map
(@ascorbic, #1026)OS | Architecture | Node |
---|---|---|
Windows | x86 & x64 | 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 |
OSX | x64 | 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 |
Linux* | x86 & x64 | 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^ |
Alpine Linux | x64 | 4, 6, 7, 8, 9, 10 |
FreeBSD 10+ | amd64 | 4, 6, 8, 9, 10 |
FreeBSD 10+ | i386 | 4, 6, 8, 9, 10 |
*Linux support refers to Ubuntu, Debian, and CentOS 5+
** Node 8 and 9 are not supported on CentOS 5
^ Only available on x64
The new version differs by 21 commits.
240e8da
4.9.1
cc6ff42
Restore old node to CI
ef713a7
Bump [email protected]
62fd84a
chore: Add info for "Pinned" label
d3aebe7
Create CODE_OF_CONDUCT.md
18d198e
typo: node-sas -> node-sass
64fdacf
chore: Add link to 2355 on PR template
8040cb7
docs: add more 404 binding install info
a3ac021
Clean out duplicate ISSUE template
e0a92f6
docs: Cleanup issue templates
94ce852
Be even more explicit that Node 10 needs 4.9
91973ed
chore: Add compile issue details to bug template
e23531d
Update issue templates using builder
8878118
docs: Add Feature request issue template
043e2bc
docs: Move and update Installation template
There are 21 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
System Information
Describe the bug
Expected behavior
yarn to complete successfully.
Screenshots (optional)
If applicable, add screenshots to help explain your problem.
Additional context (optional)
Add any other context about the problem here.
Branch | Build failing 🚨 |
---|---|
Dependency |
@types/react
|
Current Version | 16.3.14 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@types/react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The video course links to the v2 branch of the repo and you mention bit.ly/fem-ts which also takes me there. Later you mention that the reduceDict
solution will be in the repo. I found it in the v2-fem branch. That could be a potential source of confusion.
On registry https://registry.npmjs.org/
, the "latest" version (v5.0.11) of dependency travis-deploy-once
has the following deprecation notice:
We recommend to use Travis Build Stages instead
Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.
Affected package file(s): package.json
If you don't care about this, you can close this issue and not be warned about travis-deploy-once
's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:
"suppressNotifications": ["deprecationWarningIssues"]
There is no exercises folder as shown in the Challenge: 1 Color Functions video.
I was directed to post an issue on the repo after contacting support.
I am trying to run the first test on the address book challenge, following the solution and I am being given the error "No test files found". I tried to fix this using the solution shown here (#1052), which worked somewhat, but now I am running into a different error;
test/address-book.test.ts:19:27 - error TS2339: Property 'name' does not exist on type 'Function'.
19 expect(ab.constructor.name).to.eq("AddressBook");
which is not encountered in the course. I have made no other alterations to any of the files.
Additionally, despite installing chai, in the address-book.test.ts file, I am being told that module "chai" has no member "expect".
System Information
Describe the bug
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots (optional)
If applicable, add screenshots to help explain your problem.
Additional context (optional)
Add any other context about the problem here.
Branch | Build failing 🚨 |
---|---|
Dependency |
react-dom
|
Current Version | 16.3.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
react-dom is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
React.unstable_Profiler
component for measuring performance. (@bvaughn in #12745)getDerivedStateFromProps()
regardless of the reason for re-rendering. (@acdlite in #12600 and #12802)forwardRef()
on a deeper setState()
. (@gaearon in #12690)propTypes
on a context provider component. (@nicolevy in #12658)react-lifecycles-compat
in <StrictMode>
. (@bvaughn in #12644)forwardRef()
render function has propTypes
or defaultProps
. (@bvaughn in #12644)forwardRef()
and context consumers are displayed in the component stack. (@sophiebits in #12777)getDerivedStateFromProps()
support to match the new React DOM behavior. (@koba04 in #12676)testInstance.parent
crash when the parent is a fragment or another special node. (@gaearon in #12813)forwardRef()
components are now discoverable by the test renderer traversal methods. (@gaearon in #12725)setState()
updaters that return null
or undefined
. (@koba04 in #12756)There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
All tests fail (not in the expected way) with the following error:
SecurityError: localStorage is not available for opaque origins
git clone https://github.com/mike-works/typescript-fundamentals tscript
cd tscript
yarn
npm test accounts
The console should show the failing tests from the test suite, but instead I get the single error message above.
It looks like this issue is related: jestjs/jest#6766
Adding testURL: "http://localhost/"
OR testEnvironment: 'node'
to the jest.config.js
file resolved the issue for me.
Another solution is to upgrade jest
from 22.0.0
to 23.5.0
because the newest version sets the default testURL
**System Information**
Terminal: git-bash
NodeJS version: 10.15.1```
Editor: Visual Studio Code
I was following the commands as described in the FEM video flags
(https://frontendmasters.com/courses/typescript-v2/flags/) and ran into the following error when running tsc src/index.ts
:
$ tsc src/index.ts
error TS2468: Cannot find global value 'Promise'.
src/index.ts:6:14 - error TS2585: 'Promise' only refers to a type, but is being used as a value here. Do you need to change your target library? Try changing the `lib` compiler option
to es2015 or later.
6 return new Promise(res => setTimeout(res, n));
~~~~~~~
src/index.ts:20:2 - error TS2705: An async function or method in ES5/ES3 requires the 'Promise' constructor. Make sure you have a declaration for the 'Promise' constructor or include
'ES2015' in your `--lib` option.
20 (async () => {
~~~~~~~~~~~~~
Found 3 errors.
Steps to Reproduce:
$ git clone https://github.com/mike-works/typescript-fundamentals.git
$ cd tscript
$ cd examples/hello-ts
$ tsc src/index.ts
index.ts
compiled as in the videoThis issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
These problems occurred while renovating this repository. View logs.
These updates are currently rate-limited. Click on a checkbox below to force their creation now.
@commitlint/cli
, @commitlint/config-conventional
, @commitlint/travis-cli
)chai
, @types/chai
)mocha
, @types/mocha
)@commitlint/cli
, @commitlint/config-conventional
, @commitlint/travis-cli
)chai
, @types/chai
)mocha
, @types/mocha
)@typescript-eslint/eslint-plugin
, @typescript-eslint/parser
)@commitlint/cli
, @commitlint/config-conventional
, @commitlint/travis-cli
)@types/react
, @types/react-dom
)@types/react
, react
, react-dom
, react-test-renderer
)@commitlint/cli
, @commitlint/config-conventional
, @commitlint/travis-cli
)@types/react
, @types/react-dom
, react
, react-dom
, react-test-renderer
)These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.
tslint
, typescript
)These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
@commitlint/cli
, @commitlint/config-conventional
, @commitlint/travis-cli
)@typescript-eslint/eslint-plugin
, @typescript-eslint/parser
)@commitlint/cli
, @commitlint/config-conventional
, @commitlint/travis-cli
)@types/jest
, babel-jest
, jest
)tslint
, typescript
)npm
challenges/address-book/package.json
challenges/advanced-types/package.json
challenges/dict/package.json
challenges/json-types/package.json
notes/package.json
typescript 3.7.7
package.json
@commitlint/cli 8.3.5
@commitlint/config-conventional 8.3.4
@commitlint/travis-cli 8.3.5
@mike-works/js-lib-renovate-config 2.0.0
@mike-works/workshop-semantic-release-config 1.0.0
@types/chai 4.2.22
@types/mocha 5.2.7
@types/node 12.20.16
@typescript-eslint/eslint-plugin 2.34.0
@typescript-eslint/parser 2.34.0
chai 4.3.4
dtslint 0.9.9
eslint 6.8.0
husky 3.1.0
lerna 3.22.1
mocha 6.2.3
rimraf 3.0.2
semantic-release 15.14.0
source-map-support 0.5.19
ts-node 8.10.2
typescript 3.7.7
travis
.travis.yml
npm
challenges/address-book/package.json
challenges/advanced-types/package.json
@types/node 11.15.44
challenges/dict/package.json
challenges/json-types/package.json
notes/package.json
typescript 3.5.3
package.json
@commitlint/cli 8.3.5
@commitlint/config-conventional 8.3.4
@commitlint/travis-cli 8.3.5
@mike-works/js-lib-renovate-config 2.0.0
@mike-works/workshop-semantic-release-config 1.0.0
@types/chai 4.2.15
@types/mocha 5.2.7
@types/node 11.15.44
@typescript-eslint/eslint-plugin 2.34.0
@typescript-eslint/parser 2.34.0
chai 4.3.0
dtslint 0.9.9
eslint 6.8.0
husky 3.1.0
lerna 3.22.1
mocha 6.2.3
rimraf 3.0.2
semantic-release 15.14.0
source-map-support 0.5.19
ts-node 8.10.2
typescript 3.5.3
travis
.travis.yml
npm
package.json
chalk 2.4.2
@babel/core 7.9.0
@commitlint/cli 8.3.5
@commitlint/config-conventional 8.3.4
@commitlint/travis-cli 8.3.5
@mike-works/js-lib-renovate-config 2.0.0
@mike-works/workshop-semantic-release-config 1.1.2
@types/chalk 2.2.0
@types/html-webpack-plugin 3.2.2
@types/jest 24.9.1
@types/react 16.9.34
@types/react-dom 16.9.6
@types/react-hot-loader 4.1.0
@types/react-test-renderer 16.9.2
@types/webpack-env 1.15.1
awesome-typescript-loader 5.2.1
babel-core 6.26.3
babel-jest 24.9.0
babel-loader 8.1.0
babel-plugin-react-transform 3.0.0
babel-preset-env 1.7.0
css-loader 3.5.2
express 4.17.1
extract-text-webpack-plugin 4.0.0-beta.0
http-proxy-middleware 0.21.0
husky 3.1.0
jest 24.9.0
node-sass 4.13.1
react 16.13.1
react-dom 16.13.1
react-test-renderer 16.13.1
react-transform-catch-errors 1.0.2
react-transform-hmr 1.0.4
rimraf 3.0.2
sass-loader 7.3.1
scripty 1.9.1
semantic-release 15.14.0
style-loader 1.1.4
travis-deploy-once 5.0.11
ts-node 8.9.0
tslint 5.19.0
tslint-loader 3.5.4
tslint-microsoft-contrib 6.2.0
tsutils 3.17.1
typescript 3.5.3
webpack 4.42.1
webpack-dev-middleware 3.7.2
webpack-hot-middleware 2.25.0
travis
.travis.yml
Branch | Build failing 🚨 |
---|---|
Dependency | tsutils |
Current Version | 2.27.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
tsutils is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Avoid crash caused by removed function in [email protected]
.
The new version differs by 8 commits.
bed60ea
v2.27.2
627c9fe
Prepare tsutils for a future where the noop unescapeIdentifier
function is removed (#66)
da91339
Update @fimbul/wotan to the latest version 🚀 (#65)
73e9b39
chore(package): update nyc to version 12.0.1 (#63)
27b5117
Update @fimbul/wotan to the latest version 🚀 (#59)
0f5fb0c
Expose isImportTypeNode (#49)
6cb0b52
Fix tests
d518f65
Update typescript version
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
https://www.typescript-training.com/course/fundamentals-v3/07-interfaces-and-type-aliases/#extends
"If you’ve ever seen a JavaScript class that “inherits” behavior from a base class, you’ve seen an example of what TypeScript calls a heritage clause: extends"
The extends
at the end of the sentence is a link that results in a 404.
[X ] Describe the bug
yarn test
produces errors, and the test does not pass when running the solution
[ X] To Reproduce
Solution for dict exercise assumed to be located at this location
yarn test
is run in challenges/dict. produces error shown in screenshot.
I'm doing the Typescript Fundamentals on FE Masters. I've tried a few branched but none of them seem to consistently work, also it would be kinda helpful to add such information to the readme.
System Information
Describe the bug
When trying to run specific module tests, it is running all test suites instead.
To Reproduce
Steps to reproduce the behavior:
npm test dealer
./node_modules/.bin/jest --no-cache --watch $2
Test Suites: 1 failed, 2 passed, 3 total
Tests: 8 failed, 24 passed, 32 total
Snapshots: 0 total
Time: 2.083s
Ran all test suites related to changed files.
npm test fjksdlfjds dealer
This results in only the dealer suite being ran:
Additional context
See this issue which talks about the same thing near the bottom. I think the issue was closed addressing only the initial problem. Also see this possibly related issue.
Perhaps the $2 argument in scripts/test/index.sh is supposed to be $1?
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial
branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.
On registry https://registry.npmjs.org/
, the "latest" version (v2.2.0) of dependency @types/chalk
has the following deprecation notice:
This is a stub types definition for chalk (https://github.com/chalk/chalk). chalk provides its own type definitions, so you don't need @types/chalk installed!
Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.
Affected package file(s): package.json
If you don't care about this, you can close this issue and not be warned about @types/chalk
's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:
"suppressNotifications": ["deprecationWarningIssues"]
System Information
Mac OS 10.15.1 using VSCode
Describe the bug
After cloning the repo, running yarn
for a fresh install, moving into the hello-ts
example, and trying to run tsc src/index.ts --target ES2015
I get a bunch of errors surrounding the @types package showing that there are a few missing babel modules:
../../../../../node_modules/@types/babel__core/index.d.ts:13:20 - error TS2307: Cannot find module '@babel/types'.
13 import * as t from "@babel/types";
~~~~~~~~~~~~~~
../../../../../node_modules/@types/babel__core/index.d.ts:14:31 - error TS2307: Cannot find module '@babel/parser'.
14 import { ParserOptions } from "@babel/parser";
~~~~~~~~~~~~~~~
../../../../../node_modules/@types/babel__generator/index.d.ts:9:20 - error TS2307: Cannot find module '@babel/types'.
9 import * as t from "@babel/types";
~~~~~~~~~~~~~~
../../../../../node_modules/@types/babel__template/index.d.ts:9:31 - error TS2307: Cannot find module '@babel/parser'.
9 import { ParserOptions } from "@babel/parser";
~~~~~~~~~~~~~~~
../../../../../node_modules/@types/babel__template/index.d.ts:10:54 - error TS2307: Cannot find module '@babel/types'.
10 import { Expression, File, Program, Statement } from "@babel/types";
~~~~~~~~~~~~~~
../../../../../node_modules/@types/babel__traverse/index.d.ts:10:20 - error TS2307: Cannot find module '@babel/types'.
10 import * as t from "@babel/types";
~~~~~~~~~~~~~~
../../../../../node_modules/@types/babel__traverse/index.d.ts:30:5 - error TS2411: Property 'scope' of type 'Scope' is not assignable to string index type '(VisitNodeFunction<S, any> & VisitNodeFunction<S, any>) | (VisitNodeFunction<S, any> & VisitNodeObject<S, any>) | (VisitNodeObject<...> & VisitNodeFunction<...>) | (VisitNodeObject<...> & VisitNodeObject<...>)'.
30 scope?: Scope;
~~~~~
../../../../../node_modules/@types/babel__traverse/index.d.ts:31:5 - error TS2411: Property 'noScope' of type 'boolean' is not assignable to string index type '(VisitNodeFunction<S, any> & VisitNodeFunction<S, any>) | (VisitNodeFunction<S, any> & VisitNodeObject<S, any>) | (VisitNodeObject<...> & VisitNodeFunction<...>) | (VisitNodeObject<...> & VisitNodeObject<...>)'.
31 noScope?: boolean;
~~~~~~~
Found 8 errors.
To Reproduce
Steps to reproduce the behavior:
git clone https://github.com/mike-works/typescript-fundamentals -b v2 tscript
tscript
and run yarn
examples/hello-ts
tsc src/index.ts --target ES2015
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.