Skip to content
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

Path aliases not resolved in Webpack 5.0.0-beta.18 #48

Open
SquishyPandaDev opened this issue Jun 29, 2020 · 3 comments
Open

Path aliases not resolved in Webpack 5.0.0-beta.18 #48

SquishyPandaDev opened this issue Jun 29, 2020 · 3 comments

Comments

@SquishyPandaDev
Copy link

SquishyPandaDev commented Jun 29, 2020

My poject repo were this happens. Need to use beta webpack for top level await support; thanks electron. Webpack config is written in Typescript. Plugin loaded in the resolve section of the config. Run build:ts to exec webpack.

When Webpack exec get this error message:

Can't resolve '#passage' in '`${project_path}`\project_gryphon\src\renderer'

Tried using webpack alias and got the same error message.

@SquishyPandaDev
Copy link
Author

Down graded to non-beta webpack and it works just fine

@appzuka
Copy link

appzuka commented Jul 2, 2020

As you get the same error message with webpack alias it would not seem to be a problem with tsconfig-paths-webpack-plugin.

I note that if you remove the # from the filenames it all works. The plugin seems to work fine in Webpack 5 as long as you don't have # in the filenames.

@SquishyPandaDev
Copy link
Author

SquishyPandaDev commented Jul 3, 2020

Confirmed that removing # from the filenames works. I'll just stick to using @ for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants