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

Don't link local package #3247

Merged
merged 1 commit into from Mar 17, 2022
Merged

Don't link local package #3247

merged 1 commit into from Mar 17, 2022

Conversation

DukeManh
Copy link
Contributor

We've made the decision to not link local packages, both Satellite and Eslint.

@gitpod-io
Copy link

gitpod-io bot commented Mar 17, 2022

@humphd
Copy link
Contributor

humphd commented Mar 17, 2022

Comment for others reading this PR: we are going to move to using npm registry packages of things like satellite and our eslint config vs. linking in the workspace. In order to get a new version of these published, update their version in the associated package.json and push to master. It will automatically publish a new version to npm.

@DukeManh DukeManh merged commit 2bc4f3b into Seneca-CDOT:master Mar 17, 2022
@cindyledev
Copy link
Contributor

I guess that means we should prioritize getting ESLint fixes in so we can push a release. I'm getting sick of these ESLint errors :(

@cindyledev cindyledev mentioned this pull request Mar 17, 2022
8 tasks
@DukeManh
Copy link
Contributor Author

@cindyledev, yeah it's not ideal, I'm re-configuring eslint, I think the current config is a bit off

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

Successfully merging this pull request may close these issues.

None yet

4 participants