IssueRaiser

Symlink behaviour

If I add a symlink in my src directory to another directory, and then include files from that path, create-react-app gives an error: > Module parse failed: Unexpected token > You may need an appropriate loader to handle this file type. I assume create-react-app wants to have this import already built/transpiled. I would expect this to be the case for imports outside the src directory (node_modules for example). But since the symlink resides in the src directory, I would assume create-react-app would fetch these files as if they were truly in src directory. Is this a bug, or expected behaviour? It makes it really hard to extract common components.

Posted by subhero24 on Dec 4, 2017, 1:22 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments

ux (SaaS)

Symlink behaviour

subhero24Dec 4, 2017, 1:22 PM

If I add a symlink in my src directory to another directory, and then include files from that path, create-react-app gives an error: > Module parse failed: Unexpected token > You may need an appropriate loader to handle this file type. I assume create-react-app wants to have this import already built/transpiled. I would expect this to be the case for imports outside the src directory (node_modules for example). But since the symlink resides in the src directory, I would assume create-react-app would fetch these files as if they were truly in src directory. Is this a bug, or expected behaviour? It makes it really hard to extract common components.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue