-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Unable to load package metadata of ... #930
Comments
I also tested to include the yaml files via the bundle config and got an empty bundle as result {
"name": "some2-bundle.js",
"source": [
"text!**/*.yaml",
"**/*.yaml"
]
} As mentioned above I configured the loader as well "loader": {
"type": "require",
"configTarget": "vendor-bundle.js",
"includeBundleMetadataInConfig": "auto",
"plugins": [
{
"name": "text",
"extensions": [
".html",
".css",
".yaml"
],
"stub": true
}
]
} |
I will get this sorted. Meantime, temporary fix:
If you did use htmlmin, make another task
Update import processYaml from './process-yaml';
let build = gulp.series(
readProjectConfiguration,
gulp.parallel(
transpile,
processMarkup,
processYaml,
processCSS,
copyFiles
),
writeBundles
); |
i'll try this tomorrow thank you! :) |
You can try the cli branch |
Your branch seem to work for me 👍 When is the next release day? |
It should be soon. |
I've another bug for you^^ |
I'm submitting a bug report
1.0.0-beta.1
Please tell us about your environment:
Operating System:
Ubuntu 18.10
Node Version:
10.7.0
6.1.0
Browser:
all
Language:
ESNext
Loader/bundler:
RequireJS
Current behavior:
When importing a yaml file as text like this:
import 'app/feature/i18n/locale/de.yaml';
and you're using the new bundler, an error is thrown. In this case app is the source root for the application and the folder structure looks like this:The actual error is the following:
What is the expected behavior?
By configuring the loader plugin to allow the .yaml extension and adding the yaml extension to the app-bundle source expression it should be possible to import a .yaml file as text into the application.
What is the motivation / use case for changing the behavior?
To include the translation files used for i18n they must be required by the code (at least that worked previously)
The text was updated successfully, but these errors were encountered: