Skip to content
This repository was archived by the owner on Apr 16, 2020. It is now read-only.

Documentation: Migrating from --πšŽπš‘πš™πšŽπš›πš’πš–πšŽπš—πšπšŠπš•-πš–πš˜πšπšžπš•πšŽπšœ β€” Discrepancies and Considerations #16

Closed
1 task
SMotaal opened this issue Nov 29, 2018 · 2 comments

Comments

@SMotaal
Copy link

SMotaal commented Nov 29, 2018

This issue is intended to track a list of aspects destined to live in a "Migrating from --πšŽπš‘πš™πšŽπš›πš’πš–πšŽπš—πšπšŠπš•-πš–πš˜πšπšžπš•πšŽπšœ β€” Discrepancies and Considerations" document. Those are a shortlist of features which users relied on previously to address certain problems for which the new implementation either offers a more robust alternative or otherwise.

  • Default handling of index.mjs inside and outside of ESM Package Scope
    • TBD
@Trott
Copy link
Member

Trott commented Apr 8, 2020

@nodejs/modules-active-members Should this issue be moved to the main node repo or closed?

@MylesBorins
Copy link
Contributor

MylesBorins commented Apr 8, 2020 via email

@SMotaal SMotaal closed this as completed Apr 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants