generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 103
force esm via tsconfig, remove package.json creation #2084
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
Closed
josefaidt
wants to merge
10
commits into
aws-amplify:main
from
josefaidt:create-amplify-no-packagejson
Closed
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
9db24ae
force esm via tsconfig, remove package.json creation
josefaidt 63898fd
npm run update:api
josefaidt aa26514
revert client-config api update
josefaidt 22079e0
Merge remote-tracking branch 'upstream/main' into create-amplify-no-p…
josefaidt db7fe8e
revert change to platform-core api
josefaidt 4fbfce6
add changeset
josefaidt 2949c11
bump minimum typescript req to 5.4 in create-amplify
josefaidt f0232a6
re-add moduleResolution: bundler to defer resolution logic to tsx
josefaidt 5e5ebe2
remove snippet from tests for package.json
josefaidt e0768bb
Merge remote-tracking branch 'upstream/main' into create-amplify-no-p…
josefaidt File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| --- | ||
| 'create-amplify': patch | ||
| '@aws-amplify/cli-core': patch | ||
| --- | ||
|
|
||
| update create-amplify flow to init a tsconfig that forces module context, removes creation of package.json in the amplify directory |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Few things here.
esnextnext topreserve:You very likely want "nodenext" for modern Node.js projects and preserve or esnext for code that will be bundled. Why would we choosepreserveoveresnext? (unless bundling doesn't matter here anymore).preservewas added in Typescript 5.4 . If we do this we have to bump Typescript to^5.4.0. Including hereamplify-backend/packages/create-amplify/src/amplify_project_creator.ts
Line 21 in 7bf0c64
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.
for 1, bundling doesn't matter here aside from Functions.
nodenextis the one that'll force you to specify.jsfile extensions (though I think there's a new compiler option coming that'll support.tsextensions and transform).preservewill not transform your module syntax, which should yield the same results when writing with ESM syntax using import/export instead of require/module.exportsfor 2, bumped the minimum version