Skip to content

Error: ENAMETOOLONG: name too long #2585

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

Closed
aayaresko opened this issue Oct 8, 2016 · 3 comments
Closed

Error: ENAMETOOLONG: name too long #2585

aayaresko opened this issue Oct 8, 2016 · 3 comments
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix

Comments

@aayaresko
Copy link

aayaresko commented Oct 8, 2016

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Linux main 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.16
node: 6.7.0
os: linux x64

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

my app was created using CLI. the problem is that when I trying to execute ng build --aot the build process fails. apparently compiler has problems with any.component.css which contains:

html, body {
    height: 100%;
}

body {
    margin: 0;
    padding: 0;
    width: 100%;
    color: #B0BEC5;
    display: table;
    font-weight: 100;
}

.container {
    text-align: center;
    display: table-cell;
    vertical-align: middle;
}

.content {
    text-align: center;
    display: inline-block;
}

.title {
    font-size: 63px;
    margin: 10px auto;
}

h1 {
    font-size: 350px;
    margin: 10px auto;
}

my component consists of any.component.html, any.component.css, any.component.ts.

The log given by the failure.

Normally this include a stack trace and some more information.

ng build --aot
Could not start watchman; falling back to NodeWatcher for file s5130ms building modules                                                                                                            1ms add1m977ms 167ms asset 95% emitting
Error: ENAMETOOLONG: name too long, open '/www/angular/dist/html, body {                                                                                                         
    height: 100%;
}

body {
    margin: 0;
    padding: 0;
    width: 100%;
    color: #B0BEC5;
    display: table;
    font-weight: 100;
}

.container {
    text-align: center;
    display: table-cell;
    vertical-align: middle;
}

.content {
    text-align: center;
    display: inline-block;
}

.title {
    font-size: 63px;
    margin: 10px auto;
}

h1 {
    font-size: 350px;
    margin: 10px auto;
}.map'
    at Error (native)

/www/angular/node_modules/webpack/lib/Compiler.js:203
                                                if(err) return callback(err);
                     ^
TypeError: Cannot read property 'hash' of undefined
    at /www/angular/node_modules/angular-cli/tasks/build-webpack.js:38:26
    at Compiler.<anonymous> (/www/angular/node_modules/webpack/lib/Compiler.js:203:22)
    at Compiler.<anonymous> (/www/angular/node_modules/webpack/lib/Compiler.js:302:19)
    at /www/angular/node_modules/webpack/node_modules/async/lib/async.js:52:16
    at done (/www/angular/node_modules/webpack/node_modules/async/lib/async.js:241:17)
    at /www/angular/node_modules/webpack/node_modules/async/lib/async.js:44:16
    at fs.js:1305:7
    at FSReqWrap.oncomplete (fs.js:123:15)

Mention any other details that might be useful.

It's easy to reproduce: create a new app with dummy component. create a separate component.css file for that component. fill component.css file with some styles.

thanx in advance!

@filipesilva filipesilva added type: bug/fix command: build P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful labels Oct 10, 2016
@seeruk
Copy link

seeruk commented Oct 28, 2016

If it's in a separate file, are you definitely using styleUrls? I had a similar issue with a template when I had inlined the template, but was still using templateUrls.

@hansl
Copy link
Contributor

hansl commented Feb 3, 2017

Closing this as deprecated.

@hansl hansl closed this as completed Feb 3, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful type: bug/fix
Projects
None yet
Development

No branches or pull requests

4 participants