Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support independent project configuration files in Nx workspaces
See original GitHub issue🧩 Feature request
Description
In version 2 workspaces, project configurations can also be independent files, referenced by angular.json. For instance, an angular.json may contain projects configured as below.
https://nx.dev/latest/angular/core-concepts/configuration#projectjson
Currently, Scully doesn’t know how to deal with these configs not being directly present as an object in either angular.json or workspace.json.
Describe the solution you’d like
If the project in angular.json or workspace.json is a string and not an object Scully should take that path string and get the project config from the project.json in the specified project path.
Describe alternatives you’ve considered
Not sure of any alternatives at the moment.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi @sonicparke, adding
target: 'targets'solved the issue, thanks!@daton89 Do you have
target: 'targets',in your scully config file? By default, it looks forarchitectso maybe that’s the difference?