Allow non-relative imports starting with src/
or vendor/
#825
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.
Related issues
Proposed Changes
There's currently no way to use absolute import paths in Studio. This PR changes that by updating the Typescript, ESLint and Webpack configs to allow import paths starting with
src/
orvendor/
.This enables us to use a similar approach as Calypso, where import paths can start with
calypso/
.This was something I set up while working on #826. That PR introduces a new folder—
src/stores
—and I figured having a consistent import path for it would be nice.Testing Instructions
npm install
npm start
works as expectedPre-merge Checklist