-
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
ERROR when using 'ng serve' with a ./config/environment.js path #3531
Comments
This sounds like some logic leftover from If someone wants to look at it, it's probably here somewhere: There was some recent refactoring done in the forked ember code so this might or might not happen in the latest releases. |
@bdphil86 it looks like this issue was resolved by @gelliott181 so probably updating to the latest cli version would fix it. #goodnessSquad |
Thanks @aviramga. Closing this. If someone still has this issue on the latest release please open a new issue. |
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. |
OS?
Windows 10
Versions.
angular-cli: 1.0.0-beta.22-1
node: 7.2.0
os: win32 x64
Repro steps.
No. This app was created using the CLI.
I added a 'config' directory to the root of my application with an 'environment.js' file inside. I use this file from 'server.js' to set env variable in my express app.
The log given by the failure.
C:\Users\brand\Desktop\projects\ng2-skeleton-node>ng serve
app.set is not a function
TypeError: app.set is not a function
at module.exports.app (C:\Users\brand\Desktop\projects\ng2-skeleton-node\config\environment.js:2:7)
at Project.config (C:\Users\brand\Desktop\projects\ng2-skeleton-node\node_modules\angular-cli\angular-cli\lib\models\project.js:198:52)
at C:\Users\brand\Desktop\projects\ng2-skeleton-node\node_modules\angular-cli\commands\serve.js:95:40
at process._tickCallback (internal/process/next_tick.js:103:7)
Mention any other details that might be useful.
I renamed folder to 'configuration' and updated my references; this corrected the issue.
The text was updated successfully, but these errors were encountered: