-
Notifications
You must be signed in to change notification settings - Fork 12k
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
@schematics(schematic
schematics fail to run unit test with error no such file or directory
)
#12605
Comments
Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version. If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior. |
@alan-agius4 I'm using the latest version of CLI & devkit schematics. I.e. _ _ ____ _ ___
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
Angular CLI: 1.6.8
Node: 8.11.1
OS: darwin x64
Angular: undefined
...
@angular-devkit/core: 7.0.0-rc.3
@angular-devkit/schematics: 7.0.0-rc.3
typescript: 2.9.2
webpack: error Please correct me if the above details are contradicting with my statements. |
Fixed the schematics to not consider node_module specs while running unit tests Fixes #12605
Fixed the schematics to not consider node_module specs while running unit tests Fixes #12605
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PS: in short, this issue is similar to #860 from the old devkit repo. #860 was for
blank
schematic, this one is for theschematic
schematics.Bug Report or Feature Request (mark with an
x
)Command (mark with an
x
)Versions
node --version
v8.11.1npm --version
6.1.0ng --version
1.6.8Repro steps
The log given by the failure
Desired functionality
Should run tests successfully.
Mention any other details that might be useful
The text was updated successfully, but these errors were encountered: