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

v1.16.0 SyntaxError: Identifier 'process' has already been declared #6280

Closed
1 task done
bryce-pearce opened this issue May 2, 2023 · 7 comments
Closed
1 task done
Labels
bug:unverified needs-response We need a response from the original author about this issue/PR package:dev

Comments

@bryce-pearce
Copy link

bryce-pearce commented May 2, 2023

What version of Remix are you using?

1.16.0

Are all your remix dependencies & dev-dependencies using the same version?

  • Yes

Steps to Reproduce

Not sure the root cause, but this issue is appearing after upgrading Remix from 1.15 to 1.16, no other changes were made.

image

image

Note: Going through versions and it appears this issue has been occurring since at least 1.16.0-pre.4. But from that version until earlier versions have this additional error:
Cannot destructure property 'basename' of 'React__namespace.useContext(...)' as it is null.

Expected Behavior

There is no crash when upgrading to 1.16

Actual Behavior

There is a crash when upgrading to 1.16

@pcattori
Copy link
Contributor

pcattori commented May 2, 2023

@bryce-pearce could you share what (if any) future flags you have set in your remix.config.js?

@bryce-pearce
Copy link
Author

@bryce-pearce could you share what (if any) future flags you have set in your remix.config.js?

None, my remix.config.js looks like

module.exports = {
  serverDependenciesToBundle: [/^lodash-es.*/],
  ignoredRouteFiles: ['.*'],
  devServerBroadcastDelay: 1000,
};

@pcattori
Copy link
Contributor

pcattori commented May 2, 2023

Probably related to #5274 and #6259

@bryce-pearce
Copy link
Author

if anyone has updates, suggestions or workarounds, it would be much appreciated!

@HossamMarey
Copy link

If anyone has updates, suggestions, or workarounds regarding the same issue, I would greatly appreciate it!

@MichaelDeBoey
Copy link
Member

We just published version 1.17.1-pre.0 which includes #6562 (a possible fix). If you'd like to take it for a test run please try it out and let us know what you think!

@MichaelDeBoey MichaelDeBoey added the needs-response We need a response from the original author about this issue/PR label Jun 16, 2023
@github-actions
Copy link
Contributor

This issue has been automatically closed because we haven't received a response from the original author 🙈. This automation helps keep the issue tracker clean from issues that are unactionable. Please reach out if you have more information for us! 🙂

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug:unverified needs-response We need a response from the original author about this issue/PR package:dev
Projects
None yet
Development

No branches or pull requests

5 participants