-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add smoke-tests for types, build, etc #9633
Conversation
9cc348f
to
7b0eda0
Compare
fb5e4d5
to
d1de3f5
Compare
.npmrc
Outdated
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.
Without these changes not all node_modules directories have the right bins in node_modules -- for example, @warp-drive/ember did not have glint
, and would fail to build its types
bf68cd4
to
e134254
Compare
…ompilerOptions#types Fix: #9630 Fix: ember-cli/ember-cli#10611 Related: - ember-cli/ember-cli#10613 Unblocks: - ember-cli/ember-cli#10612
27208ad
to
bed0680
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.
seems odd for these to have been removed ....
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.
likely: a minor lint update / transitive dep changed the meaning of what needs to be disabled.
now: the lint-disable is only needed on the actual real implementation, not the overrides/declarations
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.
why was this needed?
private declare _isCacheHandler: boolean; | ||
private declare _finalized: boolean; | ||
declare private _isCacheHandler: boolean; | ||
declare private _finalized: boolean; |
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.
as far as I can tell TS doesn't specify the order on this nor care https://tsplay.dev/WJKaRw
declare-first does seem better though
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.
lint:fix did this
@@ -0,0 +1,34 @@ | |||
/** | |||
* These tests are more fro the out-of-monorepo tests, |
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.
* These tests are more fro the out-of-monorepo tests, | |
* These tests are more for the out-of-monorepo tests, |
/** | ||
* TODO: find another way to set this config, | ||
* because the most modern of apps will not have a compat build | ||
*/ |
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.
once embroider/macros picks a new key that's all we need. app
and __dirname
here are just for the macros API that needs them.
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.
(probably should remove this comment though)
@@ -13,6 +11,8 @@ module('it works', function (hooks) { | |||
}); | |||
|
|||
test('we can use the store', async function (assert) { | |||
// eslint-disable-next-line @typescript-eslint/ban-ts-comment | |||
// @ts-ignore this repo loads the declarations for qunit in the wrong order |
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.
// @ts-ignore this repo loads the declarations for qunit in the wrong order | |
// @ts-expect-error this repo loads the declarations for qunit in the wrong order |
@@ -17,7 +17,7 @@ | |||
"scripts": { | |||
"build:tests": "IS_TESTING=true EMBER_CLI_TEST_COMMAND=true ember build --output-path=dist-test --suppress-sizes", | |||
"_build:production": "bun run build:tests -e production", | |||
"lint": "eslint . --quiet --cache --cache-strategy=content", |
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.
accidental check-in?
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.
nay -- eslint's cache being buggy is why ci and editor and cli are sometimes not in agreement
Minimal reproduction of the problem I'm addressing: https://github.com/NullVoxPopuli/ts-types-package-json-exports-proof-for-ember-data
Description
Supersedes: #9631
Resolves: #9630
ember-data / warp-drive has enough going on it to warrant testing if new projects in various scenarios will work:
Unblocks:
Notes for the release
fix: tsconfig.json#compilerOptions#types can now use the package.json#exports paths, example:
Notes for review
NPM is not as understanding when it comes to tarballs:
the install-time peer checking here isn't as important as the post-install peer checking -- we don't want npm using the versions from package.json exactly, but the versions installed the specifiers in the package.json -- kinda surprised they have this bug, tbh