I think that the issue here as described by the is that the stuff which goes to libs is supposed to be reusable in a "standalone" manner. That means it should not really depend directly on other parts of application.
CoreModule is not a very good candidate for extracting into separate standalone lib becouse is heavily coupled with the app itself and is used in the most cases in the AppModule as mentioned above.
Example of libs style functionality can be a stateless service which does some calculation or transformation of data. The key here is that the service SHOULD receive everything from the caller.
In your example that means that only the app imports environment ( could very well do it with TS path aliases like /environment) but then passes env properties to the libs service during the function call as a parameter.
That way libs functionality remains stateless and standalone and hence more reusable.
Hope that helps! 😉
4阅读
0评论
0点赞