This repository has been archived by the owner on Aug 7, 2021. It is now read-only.
fix: execute bundle-config-loader only for the entry point of the application #829
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.
Currently bundle-config-loader is executed for any file of the application with the same name as main entry file. For example if the javascript application has app.js file located in
./app/some-folder/app.js
, the bundle-config-loader will be executed for this file.PR Checklist
What is the current behavior?
bundle-config-loader
is executed for any file of the application with the same name as main entry fileWhat is the new behavior?
bundle-config-loader
is executed only for the entry point of the applicationFixes/Implements/Closes #[Issue Number].