deno/tests/testdata/import_attributes/static_error.out

error: Expected a JavaScript or TypeScript module, but identified a Json module. Consider importing Json modules with an import attribute with the type of "json".
  Specifier: [WILDCARD]/data.json
    at [WILDCARD]static_error.ts:1:18
feat: support import attributes (#20342) 2023-09-07 08:09:16 -05:00			`error: Expected a JavaScript or TypeScript module, but identified a Json module. Consider importing Json modules with an import attribute with the type of "json".`
chore: update deno_graph and deno_doc (#13173) 2021-12-23 00:25:06 +11:00			`Specifier: [WILDCARD]/data.json`
feat: Add support for import assertions and JSON modules (#12866) This commit adds proper support for import assertions and JSON modules. Implementation of "core/modules.rs" was changed to account for multiple possible module types, instead of always assuming that the code is an "ES module". In effect "ModuleMap" now has knowledge about each modules' type (stored via "ModuleType" enum). Module loading pipeline now stores information about expected module type for each request and validates that expected type matches discovered module type based on file's "MediaType". Relevant tests were added to "core/modules.rs" and integration tests, additionally multiple WPT tests were enabled. There are still some rough edges in the implementation and not all WPT were enabled, due to: a) unclear BOM handling in source code by "FileFetcher" b) design limitation of Deno's "FileFetcher" that doesn't download the same module multiple times in a single run Co-authored-by: Kitson Kelly <me@kitsonkelly.com> 2021-12-15 19:22:36 +01:00			`at [WILDCARD]static_error.ts:1:18`