Skip to content

Conversation

@Abderahman88
Copy link
Contributor

Closes #1892

@waldekmastykarz
Copy link
Member

Thanks for the suggested fix. I'm not sure if it's the right way about it. Since this file is not shipped with the built package, I wonder if it could suppress issues that would become evident only on runtime when using CLI on Windows.

@garrytrinder
Copy link
Member

As per @waldekmastykarz comment, lets mark this as draft whilst we agree on a way forward.

@garrytrinder garrytrinder marked this pull request as draft December 1, 2020 20:27
@Abderahman88
Copy link
Contributor Author

@garrytrinder Agree. This PR still needs work 👷

@waldekmastykarz
Copy link
Member

Not sure if I'm testing this correctly, but I've added the file to a branch which I pushed to remote, deleted the local repo, cloned again, switched to the branch with .gitattributes, ran npm i + npm run build but the error persists on npm t. Is this fix supposed to fix the issue or is it meant for new files?

@waldekmastykarz
Copy link
Member

Closing this PR as we resolved the issue in #2072

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Failed test spfx project rename

3 participants