-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Permission errors after Starting 'test:client' #2374
Comments
I see this also on a fresh generation, build, test.... (plus 11 warnings from eslint that I fixed first)
Running 'gulp test' shows: Component: MainComponent Controller: OauthButtonsController Directive: oauthButtons PhantomJS 2.1.1 (Linux 0.0.0): Executed 5 of 5 SUCCESS (0.043 secs / 0.018 secs) [16:11:29] Finished 'test:client' after 2.68 s and then hangs... in the terminal. So it seems that things are a bit out of date??? perhaps. BUT I will continue to work on moving a large project built from yo last year to the most recent structure. |
Same issue here with: [10:01:35] Starting 'test:client'... cause: |
Apologies for this guys, I thought I had pushed this fix. This is the fix: webpack.make.js // Skip rendering index.html in test mode
// Reference: https://github.com/ampedandwired/html-webpack-plugin
// Render index.html
if(!TEST) {
let htmlConfig = {
template: 'client/_index.html',
filename: '../client/index.html',
alwaysWriteToDisk: true
}
config.plugins.push(
new HtmlWebpackPlugin(htmlConfig),
new HtmlWebpackHarddiskPlugin()
);
} |
Generated a generic test project (no Auth or DB - and unedited) using yo angular-fullstack then ran npm test. Got some permission errors just after Starting 'test:client' that are odd...
[00:20:55] Starting 'test:client'...
{ Error: EACCES: permission denied, mkdir '/client'
at Error (native)
cause:
{ Error: EACCES: permission denied, mkdir '/client'
at Error (native)
errno: -13, code: 'EACCES', syscall: 'mkdir', path: '/client' },
isOperational: true,
errno: -13,
code: 'EACCES',
syscall: 'mkdir',
path: '/client' }
This is happening just before Karma starts so I think the generated webpack.make.js is trying to create /client (off of root) instead of using the base directory where the project is.
Is this happening for anyone else?
The text was updated successfully, but these errors were encountered: