-
Notifications
You must be signed in to change notification settings - Fork 11
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
fix: excludedPath
contained relative paths for some prerendered static files
#74
Conversation
✅ Deploy Preview for plugin-angular-universal-demo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -74,7 +74,7 @@ Keep in mind that these will not be available on the client-side or during [prer | |||
To test this in local development, run your Angular project using `netlify serve`: | |||
|
|||
```sh | |||
netlify serve --dir dist/<your-project-name>/browser |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a follow-up to #67 (comment)
looks like the CI needs some tending |
See https://github.com/angular/cli-builds/blob/1f309514d9f8d81fb2dfbcb163b554d79394a67c/bin/ng.js#L64# Please enter the commit message for your changes. Lines starting
7b8c1fb contains an update to the minimum supported version of Node.js. This could technically be seen as a breaking change, but given that Angular compilation would fail anyways on Node versions below that, I believe it's fine to put this in a patch update. |
The logic for detecting all files in a directory was off, and generated wrong paths. This resulted in wrong paths being excluded. This PR fixes that, and adds a very simple unit test setup to prove it.