-
Notifications
You must be signed in to change notification settings - Fork 14
build: switch from required to imports in custom lib modules #1601
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
Conversation
e177024
to
6918612
Compare
dcd2221
to
206ab65
Compare
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.
A couple of questions and change suggestions.
206ab65
to
753c58e
Compare
* See the License for the specific language governing permissions and | ||
* limitations under the License. | ||
*/ | ||
|
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.
Changing extension of this file to .mjs
will need changes in README rendering as well.
This comment is also relevant to the other files in this directory.
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.
Yes, but that's in templates and since README's already resolved and examples embedded I expect this PR doesn't break it, just needs a followup in templates in upstream.
@mojito317 it turned out jest was ignoring mjs tests and once I configured it not to it became really hard to make mix of cjs and esm import styles to work together in tests. So this PR superseded by #1629 that uses |
PR summary
This is a build refactoring work that makes sure we are using esm style imports in all of our custom modules.
PR Checklist
Please make sure that your PR fulfills the following requirements:
Angular Commit Message Guidelines.
PR Type
What is the current behavior?
We have a mix of
import
andrequired
statements.What is the new behavior?
We still have
required
in generated modules, but our custom modules are now have consistent imports.Does this PR introduce a breaking change?
Other information