Chris Kent very quickly discovered an issue with the default schema the new SharePoint Framework Extensions Developer preview includes, and noted that bug here (thanks, Chris).
The summary of the issue is that f you’re working with the new developer preview, you’ll currently get a schema error on the {AppName}ApplicationCustomizer.manifest.json file located within your {AppDirectory}/src/extension folder. Originally, it will look like this:
"$schema": "../../node_modules/@microsoft/sp-module-interfaces/lib/manifestSchemas/jsonSchemas/clientSideComponentManifestSchema.json"
This is unfortunately pointing to the wrong directory, as well as the wrong file. You’ll want to update it to:
"$schema": "../../../node_modules/@microsoft/sp-module-interfaces/lib/manifestSchemas/jsonSchemas/client-side-extension-manifest.schema.json"
However, after you point this file to the correct schema, it will then detect a schema violation in your manifest, as the “*” value to denote that the version should be taken from the package.json file does not adhere to the schema’s definition, which indicates this value must be 5 characters, and it has to follow the semver.org pattern. You can ignore this warning, since things still work correctly, and the version will get substituted during the build, but the only way to remove the warning on your file, without updating the schema (not recommended), is to replace ‘*’ with the version number (i.e. 1.0.0)
I hope this helped, and if you’ve been playing with the new SharePoint Framework Extensions Developer extension preview, I’d love to hear your feedback!
Cheers,
Matt
